Experimental, hypothetical question: If I wanted two logically separate parts of the same application (sharing same resources) to run as two separate WSGI apps (say, by mapping different sub-domains to two distinctive .wsgi interface files), are there any (non-)obvious traps in this?
Of course, I keep in mind file lock contention, and possible interference in the Mako template cache, but for this hypothetical case let's say that the logical parts each have their own views, own templates, and the only thing shared is code (models, helper functions, the framework itself, auth/autz models...) and database (transactional, so concurrence is taken care of).
Why? For instance, different parts of the app might require different process/threads assignment (one suitable for multiple single threaded processes, another for fewer multiple-threaded processes), or a more obvious case is multi-site deployment of the same CMS or something (with each WSGI file defining site-specific distinctive config options), etc...
-- .oO V Oo. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
