I'm just starting to study mod_wsgi to deploy three applications based
on Pyramid framework.
The will run in apache mpm prefork 2.2, on a linux system.
I'm trying to figure out the various options given by daemon
processes, daemon group and application groups, but I'm lost between
the relations between each other.
I'f I'm not wrong, I can dedicate each app a daemon group of
processes. The flow for each application is:

1. Incoming request
2. apache evaulates the process group of the requested application
3. it starts / reuse processes (or threads) from the selected daemon
process.

First doubt:
if apache requires to spawn a new process, because of requests peaks,
how does this new process relate to the daemon processes? I suppose it
starts up a new group od damen processes. If it's right, it can
happens that two requests redirected to the same app can be processes
in two different daemns. Am I far from the truth?

Second doubt:
The application group, by default, will map an application to the same
sub-interpreter, on into the main interpreter if GLOBAL is used. What
does it mean exactly, in relation to the daemon group of processes? I
mean, how mod_wsgi guarantee that the same (sub) interpreter will be
used, if apache can spawn new processes?

Third, and last doubt:
If I set GLOBAL for the application group, but I have various daemon
groups, what is the "main interpreter"?

I'm sorry for my basic (and probably dummy) questions, but these are
my very first steps into the world of mod_wsgi...
Thanks for the help,
giovanni

-- 
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