Question #2: Must the object be serializable? I have seen a couple of
threads on that topic with no definitive answer.
-----
Sure, any data you, as the application programmer, want to keep around.
Application Data implies data that the application needs to do its job. You
can, literally, put any Object you choose in the Session data.
(*Chris*)
----- Original Message -----
From: Westland, Jonathan <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, April 26, 1999 7:31 AM
Subject: Session Object
> The API specs for javax.servlet.http.HttpSession state that:
>
> HttpSession defines methods which store these types of data:
> - Standard session properties, such as an identifier for the session, and
> the context for the session.
> - Application layer data, accessed using this interface and stored using a
> dictionary-like interface.
>
>
>
> Can anyone define "application layer data"???
>
>
>
> ----------------------------------------------------------------
> Jonathan Westland Global Software Unit
> Email: [EMAIL PROTECTED] Reinsurance Group of America, Inc.
> Voice: (314) 453-5158 660 Mason Ridge Center Drive
> Fax: (314) 453-7361 St. Louis, MO 63141-8557
> ----------------------------------------------------------------
>
>
----------------------------------------------------------------
Jonathan Westland Global Software Unit
Email: [EMAIL PROTECTED] Reinsurance Group of America, Inc.
Voice: (314) 453-5158 660 Mason Ridge Center Drive
Fax: (314) 453-7361 St. Louis, MO 63141-8557
----------------------------------------------------------------
___________________________________________________________________________
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
