Questions on mod_jk, session affinity, etc

[Jess Holle]

For cases where the session data is too large and/or volatile to 
replicate without a performance penalty and where session affinity is 
thus required, is there any hope/possibility/interest of trying to 
balance the number of active sessions per Tomcat instance (i.e. sending 
new requests to the instance with the fewest active sessions)?

Or is there any possibility of "transfering" a session from one Tomcat 
instance to another when one gets overloaded -- rather than continually 
replicating every change to the session across all instances?  [This 
would seem to require changes to Tomcat and mod_jk/mod_proxy_ajp, right?]

--
Jess Holle
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]