Robb Shecter wrote:
> Chris Pratt wrote:
>
> > Not until the 2.1 specification.
> > (*Chris*)
>
> Hi,
>
> I just downloaded the JSDK 2.1, and I couldn't find it. I did see that the
> interface HttpSession has two new methods: setMaxInactiveInterval and
> getMaxInactiveInterval. But this is a server-side timeout, correct? Is there
> another place where Sessions would expose the timeout in the cookies?
>
You are correct ... setMaxInactiveInterval sets the server-side timeout on the
session. This is true whether cookies or rewriting are used to maintain the
session.
Setting the actual parameters of the cookie that is used (if any) is servlet engine
specific, and not part of the API specification. Some engines (for example,
Tengah) allow you to modify the characteristics of the cookie in their
configuration files.
Doing this in the API would be problematic, because there is no guarantee that
sessions are being maintained by using cookies (they might be using URL rewriting
instead), and there is not any good way to client-side persist a session when that
is the case.
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
