Dropping the cache upon a graceful seems like a small price to pay to
me, but I can see others begging to differ...
William A. Rowe, Jr. wrote:
Jess Holle wrote:
I'd long since given up and been patching all the mod_*ldap stuff to
pretend shared memory does not exist on Windows.
This seems to work fine. While it would be great to have everything
similarly and well on all the platforms, what's the real downside
here given that there is only one worker process on Windows?
Actually, what's the downside if they configure one process, 400 threads
on solaris? Shouldn't we take the same optimization? Doesn't Netware
share this issue (sorry, I'm still foggy on the threads-as-processes deal
over on the Netware server.)
ap_mpm_query will tell us if we have 'sibling' processes. Simple flag,
simple exception.
The downside I can think of off hand is that if the current cache has
been designed to handle gracefuls - then poof, your cache doesn't
persist,
and that's especially bad for anyone who's set MaxRequests 10000 to mop
up any crufty third party module leakage.
Bill
