Hi,
There are no mathematical algorithms to decide whether session information
should be stored in HttpSession or Session Bean. I would say that if you
are catering to only Web Channel in your application then it you could
store session information in HttpSession or Session Bean.
If your application caters to multiple channels (WEB, Swing, WAP, etc.)
then session information should always be stored in the Session Bean.
Regards,
Milind
Dennis Xi
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
> cc:
Sent by: A Subject: Re: Why store session in
Session Bean instead of
mailing list for HttpSession?
Enterprise
JavaBeans
development
<EJB-INTEREST@JAV
A.SUN.COM>
10/11/2002 03:12
AM
Please respond to
Dennis Xi
One stateful session bean for one client. To HttpSession, it's
applicability of EJB. If HttpSession is enough, stateful session isn't
necessary.
--__--__--
----- Original Message -----
From: Fei Li
To: [EMAIL PROTECTED]
Sent: Thursday, October 10, 2002 9:24 AM
Subject: Re: Why store session in Session Bean instead of HttpSession?
Hi List,
Question:
If I create a Stateful Session Bean from a Servlet, When client A and B
use the Servlet, the container creates 2 Stateful Session Beans for each
client or creates only one Stateful Sesion Beans for both?
Thanks
Fei Li
----- Original Message -----
From: Cengiz KAYAY
To: [EMAIL PROTECTED]
Sent: Wednesday, October 09, 2002 10:59 PM
Subject: Why store session in Session Bean instead of HttpSession?
Hello List;
I wonder why someone would need to use STSB and undergo a resource usage
problem instead of just using the HttpSession.
Is the idea to use your own session object rather than storing objects
under keys in the hashtable?
Regards
Cengiz Kayay
===========================================================================
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".
