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.

would be very hard to decide where it belongs and at what place to cut it
loose.

Yeah, I'm not saying it would be easy. But if we could pull it off the
gain would be pretty big.

Eelco

Reply via email to