Pier,
>> If the next request from that client is routed to server Y, then
>> server Y will get a request with that same composite ID of
>> "serverX:sessionPPP". This tells server Y that the first thing it
>> needs to do is get the canonical version of Session sessionPPP from
>> server X. (The exact method for this may vary, but suffice to say it
>> will not involve spawning Threads from Servlets. :-) In the response
The only problem with this is you have N servers in a rotation (sprayed or
DNS round-robin) and one goes down, you lose 1/N sessions.
Some people think that if you are going to bother with session load
balancing / distribution at all, why not try and ensure all the sessions are
safe, not just a majority.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
