One use for the session ID is in debugging servlets.
In my experience with servlets so far (admittedly not vast) there have been
quite a few problems with knowing if two browser windows are operating in
separate sessions or not. The easiest way to find out is just to plonk the
ID on the page or to the server console and see if they are different or not...
-Dominic
At 10:19 PM 4/10/00 +0100, you wrote:
>Cool new address BTW.
>
>I hope they're paying you for all this.
>
>
> >Of course, this knowledge doesn't really do you a lot of good
>because
> >you cannot do much useful with the id once you have it.
>
>Are you going to suggest a depreceation for this in CAFE?
>
>It seems a logical conclusion to what you're saying (which I agree
>with).
>
>I can't see a reasons for a servlet knowing the id. I understand that
>the implementation must know but that will have access to it anyway.
>
>
>Nic
>
>___________________________________________________________________________
>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
