Radu.
To avoid such problems you may use contextes. When you have contextes
stored in the session and you store your values only in this context you
have no problem to clean the session. There is a small architecture
project called struts-it (struts-it.org) in detail
http://plstrutsit.sourcefor
At 08:14 14.03.2005, Craig McClanahan wrote:
For a developer, though, you should train yourself to good habits in
the first place -- use request scope for *everything* unless it
absolutely must be saved, on the server side, in between requests from
the same user.
This sounds like common-sense but i
On Thu, 10 Mar 2005 23:56:08 +0100, Günther Wieser
<[EMAIL PROTECTED]> wrote:
> as long as you don't have a clustered environment or session persistence
> enabled in your servlet container, there shouldn't be much difference in
> adding an object to a session or request.
That is almost, but not q
thank you all for the elaborate explaination!
--- Günther Wieser <[EMAIL PROTECTED]> wrote:
> as long as you don't have a clustered environment or
> session persistence
> enabled in your servlet container, there shouldn't
> be much difference in
> adding an object to a session or request.
>
> but
as long as you don't have a clustered environment or session persistence
enabled in your servlet container, there shouldn't be much difference in
adding an object to a session or request.
but it doesn't make sense to put it in session scope if you don't use it is
session scope, but only in request
No, it's all memory. But, you have to remember that session attributes
stay in memory for the life of the session (which typically spans many
requests and perhaps all day long), whereas request attributes stay in
memory for the life of the request. In other words, requests don't
really require
6 matches
Mail list logo
