Our site (http://www.spun.com) runs multiple Apache servers with load
balancers ("rotator box like BigIP") that distribute traffic over the Apache
servers. We have a farm of Tomcat servers. The session API's work for us.
The only problem is that Tomcat, as distributed, does not allow load
balancing persistence for the root context. We hacked a way around that
(search the archives if you're interested) - but it's an admitted kludge.
Joseph
-----Original Message-----
From: Nick Bauman [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 08, 2000 8:42 PM
To: [EMAIL PROTECTED]
Subject: Re: No revolution today
On Thu, 9 Nov 2000, Henri Gomez wrote:
> > It is important that tomcat3 has a design that allows support for
> > future
> > versions of the servlet API, but if tomcat developers don't want to see
> > it
> > happen - so be it. When Servlet2.3 will be final and in wide use, there
> > is
> > nothing that can stop someone from providing the module that supports it
> > (
> > not necesarily from apache site ).
>
> Many of us could live with a bullet proof TC 3.3 with API 2.2/JSP 1.1 for
at
> least one or two years. Note that many importants sites still use Apache
JServ
> (API 2.0) and GnuJSP.
>
I for one, would love to see the 3.x codebase's Session API actually work
"as advertised" in a web server farm with a rotator box like BigIP. Right
now the Session API in tomcat 3.1 /does not work/ across multiple
instances of tomcat in a server farm.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
