In preparing to transition a Quixote-on-mod_python application to
production I'm encountering numerous import problems after changing the
Apache MaxRequestsPerChild directive to a value greater than 1. The
symptoms are sporadic where pages are rendered successfully but error
out about every 20th to 40th time with non-existent module import
errors. Of course the module exists and refreshing the page "fixes" the
problem. (Via _q_resolve I import modules based on the URL.) With
MaxRequestsPerChild > 1 I'm also wondering if I just need to implement a
threaded publisher per quixote/doc/multi-threaded.txt.

On the mod_python list I was referred to a LENGHTY document titled,
"Module Importing Is Broken"
(http://www.dscpl.com.au/articles/modpython-003.html) which makes me
question the viability of my Quixote-on-mod_python implementation. We've
standardized on Apache so mod_python seemed like a good fit but now I'm
wondering about other implementations. Even though we are an Apache shop
should I feel constrained to Apache? Are there other Apache
implementations I should consider? Should I entertain non-Apache
solutions? If you have experience with running Quixote on multiple
servers, what's your preference?

Finally, I'm curious as to how many implementations of Quixote are on
mod_python. My sense is not many because of the comments found in
quixote/server/mod_python_handler.py. If you have experience with
Quixote/mod_python I'd like to know all the good, the bad, and the ugly.
For mere survey type responses, to prevent list clutter, feel free to
email me directly with Quixote/mod_python versions implemented type
info. Of course if you have horror stories or great successes
(benchmarked?) then it would be good to share warnings against or
recommendations for Quixote-on-mod_python with the list.


AtDhVaAnNkCsE !!!
Steve Orr
Bozeman, Montana.