I don't know what this discussion is about. It sounds like we are discussing rewriting Pytrainer as a web application with a NoSql data store.
Regarding an ORM and tight coupling to a platform, well, first of all, if we are implementing our application in Python then of course we are tightly coupled to the Python run time. This is a given - I don't think it makes sense to talk about being bound to a language. As for using an ORM, the objective here is to reduce the coupling between the business logic and the persistence code so, even though you may be adding a dependency to the code base, you are indeed increasing the flexibility and portability of the code. If this is a discussion about the future direction of the Pytrainer code base then my suggestion is Vala. As for a persistence layer, if you have decoupled your business logic from it then it shouldn't matter if you are using a document store or a RDBMS. - Nathan ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Pytrainer-devel mailing list Pytrainer-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytrainer-devel
