struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adolfo Miguelez" <>
Subject RE: What strategy for javabeans in session/request scope ?
Date Mon, 26 Apr 2004 16:54:06 GMT

I wondered from time ago the same that you.

I know a problem against the session storage option which is: under 
clustered environments, session persistence can create a heavy network 
burden, supposing affinity is not configured in the appserver,

However, the option of quering every request the model, I suspects if 
databases are able to index pages of data easily. AFAIK, scrollable 
resultsets were not available from some versions up.


>From: "Nicolas De Loof" <>
>Reply-To: "Struts Users Mailing List" <>
>To: "Struts Users Mailing List" <>
>Subject: What strategy for javabeans in session/request scope ?
>Date: Mon, 26 Apr 2004 17:28:19 +0200
>  I've worked on some applications using Struts and I haven't fond a 
>definitive response to this :
>  When a webapp uses some javabeans on many pages (as an example, a List of 
>beans and some sorting/paging actions), is it
>better to :
>  - put the list in session scope (but then, how to remove it ?)
>- call the model on every request (model should then use caching)
>- any other ?
>  Thanks for help.
>  Nico.
>To unsubscribe, e-mail:
>For additional commands, e-mail:

Protect your PC - get VirusScan Online

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message