I'm not sure why you're saying that session context is not as reliable as
cookies.
If you're only using cookies to store parameters then you're not using the full
potential of servlets. Session context allows you to store references to
objects which you can manipulate. Cookies only give you single values that you
have to parse to become digits if necessary and, most importantly, which you
actually have to transport to and from client on each request. Having a lot of
data there can slow down the transfer.
dave.
Michael wrote:
> I was wondering about what is preferable to store session information: using
> a session cookie or session parameters? Right now, my experiences with
> session parameters make me feel that cookies would be better. Using
> parameters, I have found a big difference in the reliability from one
> vserver to the next.
>
> ___________________________________________________________________________
> 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
--
David Mossakowski [EMAIL PROTECTED]
Programmer 212.310.7275
Instinet Corporation
"I don't sit idly by, I'm planning a big surprise"
___________________________________________________________________________
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
