If the data you're wanting to display is only going to be written out
to the client in one HTTP request then why not put it into the request
object rather than the session? Putting it into the request makes it
easily accessibly by .jsps that are being used to render the view and
that memory can be reclaimed when the request falls out of scope, which
should be when the HTTP request/response transaction is done.
-M@
On Monday, January 13, 2003, at 09:21 AM, Ashwani Kalra wrote:
yeah, I know this, But some body was debating this with me . He said
they
successfully did this in their last project. Actuall I want to know
more
details on how session will be strained. After all its memory either on
webserver or on app server in jvm.
Any way we are noo using request scope.
Any more details on limitation of session(Http session)
Thiharie Rajesh
<Rajesh.Thiharie@CHUR To:
[EMAIL PROTECTED]
CHILL.COM> cc: (bcc:
ashwani.kalra/Polaris)
Sent by: A mailing Subject: Re:
Keeping all the records to be displayed in session
list for Enterprise
JavaBeans development
<[EMAIL PROTECTED]
N.COM>
01/13/2003 10:01 AM
Please respond to
Thiharie Rajesh
In option two, if your number of records
are very high you will strain the Session
object a real lot. This will definitely
lead to performance degradation.
So option one is the way to go.
Your conclusion is right. :-)
Rajesh
----- Original Message -----
From: "Ashwani Kalra" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject: Keeping all the records to be displayed in session
On one of the architecture decision there are two options in our
current
project :
1. Front Controller--> jsp-->java bean/business delegate--> service
locator-->session--bean-->dao-->DB--> Displays the records
2. Front Controller-->event hander--> service
locator-->session--bean-->dao-->DB--> put all records in
HttpSession-->jsp-->retrieves record from session and displays the
records.
I suggested option 1 . because in 2nd option there are large no of
records
put in session which will strain the web server and its not scalable.
What
is your opinion ?
_______________________________________________________________________
_____
________________________
This email and any attached to it are confidential and intended only
for
the
individual or
entity to which it is addressed. If you are not the intended
recipient,
please let us know
by telephoning or emailing the sender. You should also delete the
email
and
any attachment
from your systems and should not copy the email or any attachment or
disclose their content
to any other person or entity. The views expressed here are not
necessarily
those of
Churchill Insurance Group plc or its affiliates or subsidiaries. Thank
you.
Churchill Insurance Group plc. Company Registration Number - 2280426.
England.
Registered Office: Churchill Court, Westmoreland Road, Bromley, Kent
BR1
1DP.
=======================================================================
====
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".
<InterScan_Disclaimer.txt>
===========================================================================
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".
