Isn't this app server (or web server) dependent?
For example, an alternative design is to store only a session id on the
client and store the rest of the session data in some persistent server-side
store, such as a DBMS. I believe this is the approach WebSphere Application
Server 4.0 takes, for example.
Maybe I am misunderstanding what you mean by "HTTPSession data goes up and
down the wire between the client and the web
server.".
Laurel
-----Original Message-----
From: Ian McCallion [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 30, 2001 9:29 AM
To: [EMAIL PROTECTED]
Subject: Re: EJB Session versus HttpSession
John Bateman wrote:
>
> Hi
>
> I'm assuming when you say that information passed / stored in the
> HttpSession will be passed up the wire you mean sent back and forth from
the
> App server.
HTTPSession data goes up and down the wire between the client and the web
server. It's a neat trick, because it absolves the web server from state
management, but it should be used in moderation.
<stuff deleted>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
