[Seaside] odds and ends

[Avi Bryant]

On 6/30/05, Blanchard, Todd <tobl at amazon.com> wrote:
> Ah, back button support.  We've had a huge discussion around that recently.  Basically, partial page updates don't involve the back button.  If you back off of a "rich" page, then you are leaving the app.

So, the entire session takes place on that one page then, right?

>  OTOH, hitting forwards needs to take you back to the app just as you left it.  The trick to this seems to be to make  certain that the entire state of the app is represented in hidden form fields.

That's interesting.  It seems like one model then might be to have all
communication between client and server routed through forms: you have
a javascript app on the client that's reading and writing form fields,
and a smalltalk app on the server that's reading and writing the same
form fields over HTTP (and of course some of these aren't hidden and
so you also have a user reading and writing them through the UI).  Has
anyone ever tried that?

Does the browser preserve dynamically added form fields, or just those
that were there when the page was first loaded?  Or maybe just those
with names?  (I find it a little odd that the browser doesn't simply
preserve the entire DOM tree, but what do I know)

Avi