Paul Benedict wrote:
But that of course doesn't make the list persist. Most frameworks heavily rely
on the user session
and I am now a strong believer that's the better way of doing things.
Just as a relevant side-note...
I suggest working in a distributed environment for a while and see if
your belief persists (pun intended) :)
Session replication, especially when your session object grows larger,
as they obviously will tend to in a session-heavy framework, becomes
more and more of a concern. I seem to remember IBM recommending
something like a 32k maximum for session, although I'm not sure how
accurate my memory is, the point remains that they are recommending a
value that is pretty easy to blow past without much effort.
The concern is obviously not as big when your on a single box, but even
then you need to think about session persistence, if active, which will
still incur a penalty for a larger session.
I think request scope still has a definite place in the world. This
relatively recent movement to heavy session usage still has its own set
of problems. OF course, everyone is trying to make the web more fat
client-like, me included, and that's mostly where this drive towards
session comes from.
It's interesting to me that a fairly short while ago, the use of session
for anything other than *very* simple things was a pretty highly
discouraged practice... I remember Microsoft used to say you should
almost *never* use session (or worse, application scope), everything
should be request-based. Now, I don't think *that* extreme is the right
answer, but it has been a complete 180 (I guess MS isn't the best
example, but your heard very similar recommendations from the Java camp
as well).
Frank
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
