On Sun, Jan 11, 2004 at 07:40:16PM -0800, Josh Chamas wrote:
> SessionSerialize only serializes access to the $Session object, so
> you would want to have at least as many MaxClients as there are
> possible concurrent web clients you want to support.
Oh, so if I do "$Session->{count}++;" in my script, for example, then
all other scripts are blocked while that line is executing, but
otherwise they can execute concurrently?
> I think instead if you did something like $Application->Lock in
> Script_OnStart, that would create a situation more what you are
> talking about where you would then only need MaxClients of 1 or 2,
> but I would still have it higher in that case to deal with bandwidth
> limited web clients that tie up the httpd process for longer than
> the script takes to execute.
Ahh, I see. (If the httpd process is proxied by mod_accel or something
similar which slurps the mod_perl output and spoonfeeds it to a slow
client, then I assume the mod_perl httpd's MaxClients could be 1 when
Script_OnStart calls $Application->Lock?)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
