no we didn't do that at first, the last page wasn't serialized only when it didn't because the last page anymore but that had some problems for example. We have to serialize the page before another request makes a new version.. so every request we just have to snapshot it.
johan On 10/30/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > On 10/29/07, Matej Knopp <[EMAIL PROTECTED]> wrote: > > I doubt it would prevent the page from being serialized. Versioning > > doesn't spot all changes to page (e.g. setting a property) so we can't > > rely on it, therefore we serialize it on every request. > > > > However, if you really want to get around the serialization for certain > > cases, you need to call Session.untouch(page) before > > Session.requestDetached() is called. > > > > I think calling it from Page.onDetach() should work. So you can set a > > request cycle metadata if you don't want the page to be serialized and > > then check for the meta data in page.onDetach(). > > Is this really just that component that causes the page to serialize? > Sounds like a design flaw to me if that is the case... > > Eelco > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
