Gordan Vosicki wrote:
> I seem to remember having read somewhere that a specific session
> always remains on the same server ?
>
> Any ideas ?
>
That's the way it is implemented in Apache JServ. Some servers support session
migration, using a number of different policies.
The 2.2 servlet spec clarified the rules on this topic. If you mark your web
application as <distributable> in the deployment descriptor, the server is
allowed to migrate your session (and the associated attributes, which must be
Serializable) to a different JVM if it wants to. However, at any specific
point in time, all requests to a particular session (which can happen
simultaneously) must be served from a single server. In essence, session
migration can only happen between requests.
>From the application developer perspective, this rule makes session migration
nearly transparent. You never have to worry about trying to access your
session attributes from two servers at the same time -- they will always be on
"your" server.
Session migration is not a required feature -- it is an allowed feature. Check
the docs on your particular server to understand what level of support there is
(if any) for this.
>
> Gordan Vosicki
>
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
