Yes, that would be my advice. Further, I would try and architect your
solutions in such a way as to not even require session as much as that
is possible. Clearly it won't always be, but every little bit helps :)
Frank
Lixin Chu wrote:
thank you very much - my memory is not too rusty then -
thank you very much - my memory is not too rusty then - at least I remember
the 32kb threshhold :-(
ok, so my takeaway is that, in general it is ok to use a session scoped
ActionForm with some minimum data but for large list/set we better look it
carefully. Putting them into request scope might be
On Fri, January 27, 2006 4:30 am, David Delbecq said:
> Hello,
>
> I think i read (probably on tomcat mailing list), that clustering should
> ensure (in specs) that a session is not spread across cluster (once
> session
> is started, user always speak with same jvm which started the session).
That
Hello,
I think i read (probably on tomcat mailing list), that clustering should
ensure (in specs) that a session is not spread across cluster (once session
is started, user always speak with same jvm which started the session).
Size of objects contained inside a session might however be a perf
Hi Lixin,
That was in all probability a comment I made in a thread... the 32k
limit used to be a recommendation from IBM. The reason was that in a
clustered environment, the session replication time across nodes was a
big concern. Even on a single server the container managing persistence
o
5 matches
Mail list logo
