>
> I don't pretend to understand the persistence layer or rewind (though
> I think I'm getting closer), but would this be solved by *not* having
> persistent properties and using hidden fields or some other page-
> internal (and not session-persisted) device?
>
> Todd
<snip>
It would, and it's my traditional approach. I've found though that if you
have to persist a sizeable amount of data you end up with monsterous sets of
hidden fields on every form just to persist state. It gets pretty wasteful,
so it turns out to be more efficient to just pass around a key to the client
and then back again instead of having to serialize a whole mess of data and
then stream it back.
Ultimately though I'm more comfortable with the serialize it and stuff it in
a hidden field approach as your describe. Nonetheless for this particular
app I decided to go the other way (more or less to see how well it worked).
It actually seems to be working pretty well, so I'm losing a bit of my
prejudice against server-side state. So long as there's a context key on
every page I can use to get the *right* state out of the session I'm
reasonably comfortable with how it's working out. Without that context key
though, you're lost in a fever swamp of supposition as soon as the user
presses the back button.
--- Pat
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
