Jan,
> this should not be true, i did not personally test it so far,
> but using <tcp-store/> or one of the other options should
distribute
> session data - but not to all other servers, only the next one
> in the ring.
The documentation isn't clear about this though - does this mean I can just
add tcp store directives to my <host> container and the main host will only
share session data with the next backup host? Is the srun-index still
required? If I have the following is the session only broadcast to
srun-backup id="e"?
Sorry for the raft of questions/
<!-- add clustering, define ws1-5 hosts -->
<srun id="d" host='10.240.12.4' port='6802' srun-index='4' />
<srun-backup id="a" host='10.240.12.1' port='6802' srun-index='1' />
<srun-backup id="b" host='10.240.12.2' port='6802' srun-index='2' />
<srun-backup id="c" host='10.240.12.3' port='6802' srun-index='3' />
<srun-backup id="e" host='10.240.12.5' port='6802' srun-index='5' />
<session-config>
<tcp-store/>
</session-config>
Dave
-- David Campbell Granada Sport and Interactive +44(0)207 578 4415 david.campbell@xxx.com > -----Original Message----- > From: Jan Heise [mailto:resin@xxx.de] > Sent: 25 September 2002 14:01 > To: resin-interest@xxx.com > Subject: RE: Performance/stability issues > > > hi dave, > > > We have looked at this however the main problem with Resin > LoadBalancers > > option is that sessions are not communicated afaik - people > would then > > be logged out every time they hit a new server via the loadbalancer. > > this should not be true, i did not personally test it so far, > but using <tcp-store/> or one of the other options should distribute > session data - but not to all other servers, only the next one > in the ring. > > jan > > ********************************************************************** Please visit the official Granada website at www.granadamedia.com for the latest company news. This email and any files transmitted are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify postmaster@xxx.com Thank you. **********************************************************************Received on Wed 25 Sep 2002 08:07:25 -0700
This archive was generated by hypermail 2.1.8 : Thu Sep 28 2006 - 20:17:16 PDT