Hi,
In one of our screens, we queried to the database to get all the
result sets (from a stateless session bean), and we need to have these
result sets in most of the screens. We are having two solutions with us to
complete this. Please suggest one best solution among these with the valid
and proper reason.
1. Can we make the stateless session bean to stateful session bean
to handle all the data (along with methods), and we can then call the same
EJB instance (using Handle) in other screens?
2. Can we keep all the result sets as session objects/variables in
HTTP session?
Regarding this I have the following queries:
1. Is the HTTP session data is live data?
2. If we keep all data directly in HTTP session, is it will
over-load?
3. Is the HTTP session data decreases the performance?
4. What's the exact difference between both (performance-wise) ?
Thanks in Advance,
Srinivasa Rao Chintala.
===========================================================================
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".
HTTP Session Vs Stateful Session Beans
Rao, Chintala Srinivasa (CAP, FLEET) Wed, 21 Jun 2000 17:24:37 -0700
- Re: HTTP Session Vs Stateful Session ... Rao, Chintala Srinivasa (CAP, FLEET)
- Re: HTTP Session Vs Stateful Ses... Juan Pablo Lorandi
- Re: HTTP Session Vs Stateful Ses... Rao, Chintala Srinivasa (CAP, FLEET)
- Re: HTTP Session Vs Stateful Ses... Juan Pablo Lorandi
- Re: HTTP Session Vs Stateful... David Wall
- Re: Pagination [was: Re... Joel Shellman
- Re: HTTP Session Vs Stat... David Regan
- Re: HTTP Session Vs ... Gary Shea
- Re: HTTP Sessio... David Regan
- Re: HTTP Sessio... Aravind Naidu
- Re: HTTP Session Vs Stateful Ses... Srinivas Ganapur
