On 2/2/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
On 2/2/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
> ofcourse in the end everything is the page
> But what to do for example with the component that is in both places?
> (the component that is removed from the parent but still kept in the page
> for later attachement)
The first pass would serialize the whole page and index it so that we
can easily find it back later. If we do custom serialization, we could
take some heuristics into account like the component path/ ids and
such.
So, this would work the opposite of what we're doing now. Rather than
rolling back, we would start with the first version of the page (which
is fully serialized) and then apply the changes up to the version we
need. This may or may not be more expensive depending on how many
version there would be and what version is rolled back too, but in
terms of serializing and saving state (including disk or network
access) it would for certain be cheaper.
Eelco
