On Fri, Oct 22, 2010 at 1:14 AM, Graham Dumpleton
<[email protected]> wrote:
> As to further changes to mod_wsgi itself to support further hooking in
> Apache, that will almost certainly never happen. It has already got
> too messy as it is.

Understood.

I guess I see a couple different purposes for mixing Python with Apache.
The first/primary is to use Python to provide dynamic content, and for
this I'm certainly of the opinion that WSGI (mod_wsgi) is the best way
to proceed.

But the other purpose is to allow Python to be used in many places
where Apache can be "customized", and this includes its use in many
of the hooks, etc.

Obviously the deprecated mod_python tried to do both. But if its
too complicated (or a costly diversion) mod_wsgi probably should
just concentrate on the WSGI part.


I may actually play with making a separate module specifically to
try to cover Apache hooking, but not to compete with the main
content-providing as with mod_wsgi. I may do this mostly just to try
to strengthen my own personal knowledge and confidence of dealing
with Apache internals; maybe nothing will come of it, but who knows.

So a few questions Graham:

Have you then pretty much shelved any idea of resurrecting some
of the missing mod_python like functionality at this point?

A separate module would still need to interact with the Python
states, threads, and interpreters. Probably it would require
mod_wsgi so it could re-use the interpreter management.
Do you have any specific notes on how to best be compatible
with mod_wsgi, especially for initialization? (do it the mod_python
way, or is there something better to do)?

If I wanted a way to pass information up through an early hook into
mod_wsgi, do you think the ap request notes table is a reasonable
mechanism?

Thanks
-- 
Deron Meranda
http://deron.meranda.us/

-- 
You received this message because you are subscribed to the Google Groups 
"modwsgi" 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/modwsgi?hl=en.

Reply via email to