I have a bit of non-pyramid/sqlalchemy insight / warnings for this: with this design pattern, you're going to need to pay close attention to the database server setup, and (probably) either disable connection pooling or create some sort of management for it. depending on usage, you have the potential to run close to tying up the max_connections.
also - is there any reason why you're entirely replacing the database connection? you can easily have multiple database connections / sessions. keep all of your "application" logic (and auth) on one session; keep all the user/client stuff on a second. just address/use sessions uniquely. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discuss+unsubscr...@googlegroups.com. To post to this group, send email to pylons-discuss@googlegroups.com. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/d/optout.
