[Seaside-dev] snapshotting state after rendering

[Julian Fitzell]

On Sat, Jan 17, 2009 at 6:29 PM, Lukas Renggli <renggli at gmail.com> wrote:
>> I wonder whether the RenderContinuation couldn't/shouldn't just pass
>> its Snapshot into the next ActionContinuation. The ActionContinuation
>> would create a new Snapshot after running callbacks and pass it to the
>> RenderContinuation.
>
> That should work. We have to try.
>
>> For Javascript callbacks, the ActionContinuation would probably want to do:
>>
>> (states := states copy) snapshot
>>
>> in order to avoid modifying the state of the previous render (though
>> maybe not? Lukas will know what the correct semantics are for that).
>
> The AJAX callbacks are essentially the same as the navigation
> callbacks. In this case the callback processing and the rendering fall
> into the same request.

Well, they also currently snapshot (update) the Snapshot in the
ActionContinuation which navigation links do not. If the Snapshot is
shared with the previous RenderContinuation, that would mean that
hitting Reload would use the updated state. Perhaps this is desired
(?) but it is not the current behaviour.

Julian