struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Riyad Kalla <>
Subject Re: What strategy for javabeans in session/request scope ?
Date Mon, 26 Apr 2004 15:38:21 GMT
I have many situations like this and tend to put it in the session with a 
well-known key. The reason for this is that leaving it in the model, or 
putting it in the session (assuming the model caches) will take the same 
amount of memory, but putting it in the session is easier to get to 
especially for taglibs.

Keeping your session clean is important, but I wouldn't say so critically 
important that you should introduce that level of complication.

Anyone else have an opinion?

On Monday 26 April 2004 08:28 am, Nicolas De Loof wrote:
> Hello,
>  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:

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

View raw message