when a developer decided to go for a stateless session bean , why does he
need to keep the state ? if he want to cache the date he gathered from DB,
he should use entity bean , where
he can cache ( IMHO entity beans are not limited to cache ) , keeping more
and more data into http session may not be a good idea, when it grows it
might be difficult to manage and scale. The http session may be used to hold
the state of a html screen and few encrypted keys but not the data from the
DB. I would suggest to use stateless session bean and entity bean together
to address your requirement.
-- Ahimanikya
> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of James Cook
> Sent: Thursday, February 17, 2000 5:28 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Caching data in an stateful session EJB???
>
>
> Typically, when dealing with stateless session beans (SLSB), state
> information is kept on the client. Each request to the SLSB includes a
> parameter representing the state information. Sometimes this can
> just be an
> id field, other times it may represent a more complex object.
>
> If you are working through a servlet engine (or web server) you
> may be able
> to take advantage of the HTTP session object.
>
> These are not the only places state can live, but if you want to
> keep it on
> the server-side (and you are not using servlets), you are better off using
> Stateful Session Beans.
>
> jim
>
> ----- Original Message -----
> From: Peter Delahunty <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, February 16, 2000 9:22 AM
> Subject: Re: Caching data in an stateful session EJB???
>
>
> > >If we use stateless session beans, where can we cache the
> > > data retrieved from the database?
> >
> > To overlap here a bit Can someone explain to me how you can use a
> stateless
> > session bean to cache information taken from a database. If the EJB is
> > stateless then where do you store the information.
> >
> >
> >
> > -----Original Message-----
> > From: Jeff Davidson [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, February 16, 2000 12:53 AM
> > To: [EMAIL PROTECTED]
> > Subject: Caching data in an stateful session EJB???
> >
> >
> > We are designing a system based on J2EE and EJB which needs to service
> > thousands
> > of client applications. Originally we thought that each client would
> > interact
> > with one stateful session EJB in order to collect & cache data
> pulled from
> > corporate databases. However, ass I've been reading more on EJBs, it
> sounds
> > like this may not be a very good approach in terms of scaling and
> > performance. If we use stateless session beans, where can we cache the
> > data retrieved from the database? We need the data for subsequent
> > calls to a rules-based engine to have it process and return information
> > which we then return to the client app. Then, as we collect information
> > from the client app, we need to combine this with the data from the
> > db to be able to make more requests to the rules-based engine.
> So we need
> > to cache it somewhere, but where?
> >
> > The machines we're running this stuff on are HP K380 w/2 CPUs and
> > 2 GB memory. We expect to start with 1000 simultaneous clients scaling
> > up to 6000 for the call center. Then we will have the web clients to
> > worry about on top of that, which will likely be 1000's more. Each
> channel
> > (web and call center) will have it's own HP K380 (2 cpus) running the
> > WebLogic app server.
> >
> > Thanks in advance for any advice/information.
> >
> > Jeff
> >
> >
> ==================================================================
> =========
> > 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".
