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