[Seaside] expiring pages

[radoslav hodnicak]

On Thu, 22 Jul 2004, Avi Bryant wrote:

> However, I personally prefer to allow the user to use as many browser
> windows as they want to.  The only real solution here is what Julian
> suggested - don't operate on the real model object, but on a working
> copy of it, and then copy that back into the real object when the user
> hits save (rollforward?).  This is where a proper in-image
> transactional system would be really nice, as we've discussed before.

I do have in-image transactions, from glorp (they only work on glorp
objects but that's fine). I've just realised that I should use them
backwards - my editor should operate on the copy saved by glorp for
restoring the object, and do rollback on save and commit on cancel.

lol this is twisted

rado