On 1/6/06, Jonathan Locke <[EMAIL PROTECTED]> wrote:
i dont know if this is all that possible without breaking component encapsulation. components might have internal state that the user cannot get to so it cannot be made part of ipagemapentry.
Igor Vaynberg wrote:
> possibly the fact that pages with large component hierarchies ( ie
> pages with repeaters ) will be huge when serialized and base64ed. so
> you end up with client side pages that are huge - this is pretty much
> exactly what jsf does.
yep. but as i was saying... if you care, you can get rid of the
majority of that (all the component state and overhead that doesn't
really matter) by implementing IPageMapEntry. you're trading time for
space.
i think this is doable for simple pages, but for more complex ones i dont know.
-Igor
