On Mar 22, 2010, at 01:46 PM, Jennifer Redman wrote:
Since Django is being used for the web-interface I'm curious about the implications for the ORM. Since MM 3.0 is using STORM - do you plan to just not use the built-in Django ORM and go with STORM - or are you going to wind up with 2 different database interfaces?
Great question. I'm not a Django expert so I'm open to suggestions, but since these are in a sense separate projects and their primary (only?) integration point is the REST API, I think it would be okay to use the Django ORM for the web ui and Storm for the core engine. Ideally, the web ui would only have enough model code for it to do its job, possibly including caching where necessary, storing and accessing most of the core data in the engine via REST.
The place where things might get tricky is in authentication, and I'm not really sure what the right answer is. My sense is that if we can store that in the core and provide it over REST that will work better.
-Barry