> What is recommended: > 1. A different turbogears project for each "business app" which > would then > require a different port. Requires a little config management to keep track > of the ports, but separates them better, and allows independent restart. > > 2. Or a single project with a "subcontroller" for each business app. > Provides a single "master node" and everything under that. In a small > company (I'm the only Python programmer) this provides ease of tracking > what's "out there".
I would go the second route personally. You'll have less memory consumption, cleaner URL structures, and easier deployment. But I would guess that there might be other things that push towards the first option. You mention independent restarts, which is an advantage and a disadvantage (you need ot monitor them all, and make sure they are all up.) If you hadn't mentioned that traffic was not an issue, that would be another thing to consider. ---Mark --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
