Maybe mention the differences (if any) or a short example of setting up multiple apps? Is just another apache block/stanza with the appropriate dir in PythonPath all that's needed?
[As an (old) Ian blog post discussed, this is something PHP makes super easy and a common situation for many -- lots of scattered disparate little applications rather than monolithic, uber-apps. But then there's also the paste composite app thing... hmm. When to use which? Yes a different topic, sorry!] I think I'm veering into apache/modpy issues, not Pylons specifically. Going further, am I correct in assuming if you have 3 apache modpy children, the interp + app runs threaded in each? So in theory you're getting a lot more request-handling from those 3 than from 3 modperl processes which aren't running threaded? I am probably going to be proxying to back-end modpy's like the common modperl setup, so I'm trying to relate the different processes/threaded issues ... thanks as usual. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
