We serialize the page every time it's touched. And the page is touched
every request. There is no easy way to determine whether a page jas
changed during the request, so we just serialize it. Otherwise we would
have to traverse the entire object tree and check every property for
being changed. Kinda overkill, don't you think?
In next version of wicket we should have this simplyfied, so that it is
much easier to tell wicket not to serialize the page in cases when the
page doesnt' change and the serialization would cause unnecessary
overhead, such as some ajax polls or autocomplete requests.
-Matej
Eelco Hillenius wrote / napísal(a):
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
