Session afinity is often mandatory when in situations where parts of applications are not just data, ie when your web-application is used to discuss with a real-time system requiring that all the app session came from the same JVM.
And so the session afinity must be configurable. - Henri Gomez ___[_]____ EMAIL : [EMAIL PROTECTED] (. .) PGP KEY : 697ECEDD ...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 >-----Original Message----- >From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] >Sent: Monday, December 17, 2001 7:38 PM >To: Tomcat Developers List; Tom Drake >Subject: Re: Configuring Multiple Tomcat JVMs with Apache - Load >Balancing > > > > >On Mon, 17 Dec 2001, Tom Drake wrote: > >> >> Keep in mind that with distributed sessions (coming soon to a tomcat >> near you), affinity is no longer 'required' in order to >function. This >> provides the added benefit of fail-over. > >As I mentioned in a thread about this on TOMCAT-USER, there >*are* session >affinity requirements in the servlet specs (both 2.2 and 2.3) >that should >be obeyed. > >Craig > > >-- >To unsubscribe, e-mail: ><mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: ><mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
