Thanks to all you guys for such elaborative inputs! Quite valuable for TG practioners like me.
> Second reason I choose mod_Wsgi /apache over reverse proxy is the fact > that apache starts and stops my app, my logs are unified in one apache > log file(including log rotation). There is no need for other programs > to supervise my tg app. You can use apache to serv your static content > . Can't beat the 4 lines of configuration in apache config file. > > Why would you go the harder way? > Lucas This seems a valuable tips. If the performance is more or less same, it tempts me to learn this method, but before that a few layman apprehensions: 1. Is scaling up (by running multiple proceses on one or more boxes) any difficult using this option, compared to the reverse proxing? I guess no. 2. Does this option hold good for TG 2.0/Pylons as well? I guess yes. 3. Any disadvantage in this option, for high traffic sites, compared to the other methods? thanks Sanjay --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
