...or you could take the "easy cheesy" approach and simply write the
same data to all of your session servers and then round-robin between
them. In practice I've found the fail over code hard to write well,
and seen many developers try and fail with this approach.
- n
On Sep 23, 2005, at 3:19 PM, Bas Scheffers wrote:
On 23 Sep 2005, at 19:51, Daniel P. Stasinski wrote:
The idea of a dedicated session server solves all the problems of
multiple servers, multiple instances and load balancing.
Well, you'll have to have multiple session servers with fail-over
too! :)
If you use persistence to disk in my implementation - and that disk
is a SAN cluster all web servers connect to - and use sticky load
balancing, you also don't have a problem. Say I have a session that
keeps comming back to server A and that server fails, the balancer
would start sending me to server B. It will find the session on
disk, cache it and all will be hunkydory.
Bas.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to
<[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the
Subject: field of your email blank.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
