hihi all,
i think we have trade-offs to both ways of persistence here...
if i may ask:
for Brian:
- if you are not using ActionForm objects (nor any Struts tags for
that matter, if you're only using <c:out> and POHTML), then what
features of Struts are you using?
i'm just trying to understand the context better behind this discussion
since the answer *always* depends on the context. is your web app
really simple? very little business rules validation, and no need to
i18n? are you not worried about having all those hidden values being
seen (by viewing html source)?
what about performance? adding more information that needs to be sent
across the network will not necessarily affect latency, but it *will*
affect response time, and this is what the users experience will be
based on for any web apps.
for Rick:
- if and when your web app does experience OutOfMemoryExceptions due
to sheer volume (of users/sessions), then what can you do to fix this?
i also worry about this possible eventuality and try to use session
judiciously, but even then in theory, it is still going against finite
memory resources.
do you just keep maximizing the server memory, and/or keep adding
servers (clustering/load balancing)?
and when you talk about state persistence, the issues of concurrency
follows closely as well although it is a problem independent from the
immediate discussion... i only bring it up because imo it is a risk
factor that should be considered when thinking about state persisting
strategy.
woodchuck
--- Rick Reumann <[EMAIL PROTECTED]> wrote:
> But that's my point, if you server is going to crash because of bean
> stored in Session scope that is holding simple properties, than there
>
> are some serious issues with your server set up. What's ironic is I
> bet
> you'll end up with a slower performance (at least from the user's
> perspective) doing the other tricks you'll need to do in order to get
>
> all of this to work using only the Request.
>
> I totally agree in not use the Session for unnecessary operations
> that
> do you not need persist, but for what you are doing is the exact
> reason
> you have the Session. Do you think shopping carts persist all their
> contents into hidden properties on each page as the user browses a
> shopping site?
__________________________________
Yahoo! Messenger
Show us what our next emoticon should look like. Join the fun.
http://www.advision.webevents.yahoo.com/emoticontest
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
