Hi Christopher,
Thanks for your answer.
Does that mean that the session object itself is always passed to all servlets also
running across different JVMs and that no change at creating and using the session
object is necessary? Is the session object therefore made Serializable?
Therefore if I would not store any objects in my session the session would work fine
for authentication and session timeout
purposes also across different JVMs?
Only if I want to store objects I have to make them Serializable?
I am using the cookie method to store the session Id. Do you know what is stored in
the cookie:only the sessionId or also the timestamp of the latest click?
Axel Lannion/France
> -----Original Message-----
> From: Christopher K. St. John [SMTP:[EMAIL PROTECTED]]
> Sent: jeudi 22 f> évrier 2001 20:18
> To: [EMAIL PROTECTED]
> Subject: Re: sessions across multiple servers
>
> Bartsch Axel wrote:
> >
> > If you want a session across multiple JVMs on the same server
> > is this in principal the same problem as for sessions across
> > multiple servers? Does the session API have a solution?
> >
>
> Yes to both. The basic idea is that you either:
>
> a) Make all the objects in your session Serializable,
> and the container streams them over to the appropriate
> JVM as needed, automagically.
>
> b) Use some sort of container-specific mechanism.
>
> There's an outline of the requirements in the 2.3 spec,
> section 7.7.2.
>
> <URL:http://java.sun.com/products/servlet/download.html>
>
> The thing is, not all containers support distributed
> sessions. "Distributable" webapps were introduced
> in 2.2, but they're optional. So you need to check
> the documentation for your particular servlet container
> to see what's possible. If it's a commercially supported
> container, then I guarantee that there's some info
> someplace on the vendor's website about how to set
> things up. The aforementioned advanced-servlets thread
> has some discussion about how particular containers
> (like WebSphere or NAS) handle things.
>
>
> -cks
>
> ___________________________________________________________________________
> 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
___________________________________________________________________________
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
