Re: FW: [advanced-servlets] Session Load Balancing (was: To avoid

Nick Bauman wrote: > Jason, > >> Yes, and the way I've seen people solve this issue is to make each >> server constantly replicate its sessions to another server so that any >> session's state is stored in two servers (not just one). For example, >> if you've got four servers, A, B, C, and D, y

Re: FW: [advanced-servlets] Session Load Balancing (was: To avoid

Jason, > > Yes, and the way I've seen people solve this issue is to make each > server constantly replicate its sessions to another server so that any > session's state is stored in two servers (not just one). For example, > if you've got four servers, A, B, C, and D, you configure A to > repli

Re: FW: [advanced-servlets] Session Load Balancing (was: To avoid

Nick Bauman wrote: > 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 sessionP

Re: FW: [advanced-servlets] Session Load Balancing (was: To avoid

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 ex

FW: [advanced-servlets] Session Load Balancing (was: To avoid Duplicate Login)

Really interesting, when thinking about load balancing... Pier -- Pier Fumagalli -- Forwarded Message > From: Charles Forsythe <[EMAIL PROTECTED]> > O