C�dric Janssens wrote:
> >[snip part of the answer about QAHT implementation]
>
> >On a more philosophical note, though, you are making an implicit assumption
> that
> >there is only one instance of your servlet class, in one JVM, in existence.
> That
> >might be true, but it definitely won't be in a distributed servlet engine
> >environment that lets you load balance access to the same servlet across
> multiple
> >independent server machines.
> >
> >Craig McClanahan
>
> Is there distributed servlet engine environment that lets you load balance
> access to the same servlet across multiple independent server machines
> available nowdays?
Apache JServ contains code that accomplishes this particular feat in the 1.0
beta release. You can start as many servlet engines as you like for the same
servlet zone (pretty much equivalent to a servlet context) -- on the same or
different servers as your web server.
Currently, the load balancing works like this:
* Requests not connected to a session are randomly
distributed across the available servlet engines.
* Requests that are connected to a session are
always returned to the same servlet engine, so that
HttpSession stashed information does not have to
be moved around.
For more information, see:
http://java.apache.org
Craig McClanahan
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
