That sounds like the right solution! I think I remember the status page from jk2, and it is a good idea.
-Michael Greer
On Feb 19, 2005, at 2:29 PM, Mladen Turk wrote:
Michael Greer wrote:Should I take the trouble?
local_worker and local_worker_only flags will be deprecated. (already are with the current 1.2.9-dev) There has been more powerful mechanism implemented, that is IMO more clearer and acts like it should. 1.2.9 has shared memory and status page that can be used to dynamically change worker properties at runtime, without the need for graceful restarts, or something like.
New directives like 'redirect' (for preferred failover), 'disabled' and 'sticky_session_force' has been added.
The documentation will be updated accordingly. Release plan is for the first half of march.
Like you said the entire concept of local_worker and local_worker_only was too fuzzy and understandable to a wider audience.
Regards, Mladen.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
