Has anybody tried mixing code that uses SQL Object (for authentication and database access) with code that uses SQL Alchemy (for the same purposes)? The code that uses SA would import the model with SA, the code that uses SO would import the model with SO. But cookies, user maintenance, etc. would be done at the big piece with SO only.
I'm interested in plugging in a new module on an old system without having to change one of the two (probably the smaller newer piece would be changed to use SO). With that, I'd like to reduce the load on the system (no more 2 daemons) and migrate old code a piece at a time. The alternative of having them as separate "entities" is what I do now, i.e., the new module is running by itself with its own daemon, config set, etc. -- Jorge Godoy <jgo...@gmail.com> -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to turboge...@googlegroups.com. To unsubscribe from this group, send email to turbogears+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
