On Feb 11, 3:46 pm, Robin Becker <ro...@reportlab.com> wrote: > well the flup server for fast cgi supports forking if the server is declared > as > an external process in apache. Then the top level of the flup process handles > each request and passes it off to a forked worker. I cannot recall exactly, > but > I believe that apache mod_fastcgi does the right thing when it comes to > internally declared fastcgi handlers. For apache at least I think the > threading > issues are handled properly. > > I think the preforkserver.py code handles all the threading issues for you > (assuming it's not win32).
Thanks - I think if I go the flup route I would use AJP though - since its very easy to setup with apache (1 proxy line) and mod_ajp comes as standard. And then everything is very much seperated from the apache process. -- http://mail.python.org/mailman/listinfo/python-list
