State of TurboGears running with Apache?

[Graham Dumpleton]

>From what I have read, there has in the past been some questions marks
on whether TurboGears will run properly under Apache using mod_python.
Part of the reason seemed to be that Apache runs as a multiprocess
server and database caches in individual processes aren't being
synchronised. The result of this could be that depending on which
process handled a request, one might get old data being displayed in a
page.

What is the current state of play with using TurboGears in a
multiprocess web server such as Apache? Is this still, or was it ever
an issue?

The documentation for using TurboGears with mod_python still mentions
potential database problems.

http://docs.turbogears.org/1.0/mod_python

FWIW, I have had a recipe up for a while now on how to use TurboGears
with mod_wsgi (www.modwsgi.org). This documentation has recently been
expanded to show how to run TurboGears in daemon mode, a possible
solution for the multiprocess server problem. Use of daemon mode also
means the application can be run as a distinct user and moves the
memory overhead out of the Apache child processes.

I haven't mentioned on the list before that TurboGears can work with
mod_wsgi, so whether anyone has stumbled across the fact that it does
work and tried it I am not sure. For anyone who is interested, the
documentation for using TurboGears with mod_wsgi is at:

http://code.google.com/p/modwsgi/wiki/IntegrationWithTurboGears

Would sort of be nice to know whether the database caching issues are
in fact a problem or not so I can ensure the documentation is up to
date.

If anyone has tried TurboGears with mod_wsgi, would also be nice to
get some feedback on whether it works or whether I need to add
additional details to the documentation.

Thanks.

Graham