I don't expect the standard deployment of TG2 to be much different than TG1. We'll have a process (some wsgi server) that is long-running, and AFIK that's the general way that pylons is deployed right now too.
FastCGI may be supported, but it's far from the default in pylons anymore... Seems like lots of people are using ModWSGI these days. --Mark On Feb 4, 2008 4:07 PM, Felix Schwarz <[EMAIL PROTECTED]> wrote: > > I like to high-jack this thread for some general question about the > scheduler in TG2. > > As far as I understand, TG2 will be based on Pylons which seems to use a > FastCGI configuration (at least as recommend production environment) > instead of a custom server like CherryPy. If this is true, it has some > serious implications for "server plugins" like the scheduler or TurboMail. > > Previously we could rely on the server which was always available. FastCGI > processes will be killed after a certain amount of request (or a configured > time) so it must not be assumed that at least one process is always > running. (Am I completely wrong?) > > Do you have some ideas how to deal with this problem? > > fs > -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
