> Of course if the web-server goes down and your
> load-balancer redirects the user to another server you will lose that
> session.

This is not necessarily true. If your session information persists as a cookie
and your servers support fail over technology then the user may experience a
little hiccup, but they won't loose their session. If you're interested in this
sort of ultra-reliable web server technology check out the ART Technology
Group's Dynamo server suite. Sun and MySun all run on Dynamo servers using
load-balancing and fail over technology giving us 24/7 availability.

The ART Techonology group can be found at: http://www.atg.com

Sun and MySun are located at: http://www.sun.com and http://www.sun.com/mysun

Cheers!
Ian C.


> Kevin Jones wrote:
> >
> > If we use the session api from a servlet (or JSP) then the session
> > information is stored on the web-server (yes?) and a cookie (assuming
> > cookies are enabled) is sent to the agent with a session id. Suppose we have
> > a web-farm - looking in the Servlet API it doesn't mention what happens in
> > this case. i.e. what happens if I have more than one web server servicing a
> > site - where are server-side sessions stored? does any web-server/servlet
> > engine offer this capability?
> >


         ______
        /_____/\
       /____ \\ \          Ian R. Chesal - HQ Marketing Intern
      /_____\ \\ /
     /_____/ \/ / /        Sun Microsystems of Canada, Inc.
    /_____/ /   \//\       Phone:  905.415.7958 (x57958)
    \_____\//\   / /       Fax:    905.415.7991
     \_____/ / /\ /        E-mail: [EMAIL PROTECTED]
      \_____/ \\ \
       \_____\ \\
        \_____\/

___________________________________________________________________________
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

Reply via email to