And you keep track of this stateful session bean how? Where are you storing
the handle to the bean when the user switches pages?

-David

-----Original Message-----
From: Achen, Kiran On Behalf Of Achen, Kiran
Sent: Wednesday, June 07, 2000 7:12 AM
To: [EMAIL PROTECTED]
Subject: RE: Servlet sessions vs statefull session beans


HttpSession is useful to store the state in cases where the app server
guarantees the same HttpSession. There are other instances like Palm VII
applications where every time a request is made, a new HttpSession is
created. In this scenario, using HttpSession will not work. I only can
think of Palm VII applications which will have this problem at present.
In this scenario you will have to use stateful session bean for session
tracking.

Kiran

   ----------
   From:       EJB-INTEREST(a)JAVA.SUN.COM
   Sent:       Tuesday, June 06, 2000 12:30 PM
   To:         EJB-INTEREST(a)JAVA.SUN.COM
   Cc:         dtrieu(a)EBUILT.COM
   Subject:    Re: Servlet sessions vs statefull session beans

   If you over use and depend on HttpSession to store your session data,
   and your
   servlet engine is clustered.  Do you know what happen to the
   performance/resource of your system, especially in a heavy hits site.

   yu_robin wrote:

   > I use servlets to store session data because these data can be
   simply
   > transmited to JSPs and other Servlets.
   >
   > > ----------
   > > From:         Jim Archer[SMTP:[EMAIL PROTECTED]]
   > > Reply To:     A mailing list for Enterprise JavaBeans development
   > > Sent:         Tuesday, June 6, 2000 10:38 AM
   > > To:   [EMAIL PROTECTED]
   > > Subject:      Servlet sessions vs statefull session beans
   > >
   > > Hi All...
   > >
   > > I am interested in peoples opinions on the relative advantages
   and
   > > disadvantages of servlett sessions and statefull session beans. I
   have
   > > read
   > > many places that statefull session beans are inefficient, since
   they
   > > instantiate a bean that lives as long as a client does, and there
   is one
   > > per client.
   > >
   > > I'm wondering how this overhead compares to useing session data
   in a
   > > servlet? Is the servelts mechanism for storing session data more
   efficient
   > > than using a statefull session bean? In general, which mechanism
   do people
   > > use?
   > >
   > > Thanks!
   > >
   > > Jim
   > >
   > >
   =====================================================================
   =====
   > > =
   > > 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".
   > >
   > >
   > >
   >
   >
   =====================================================================
   ======
   > 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".

   =====================================================================
   ======
   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".

===========================================================================
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".

Reply via email to