First, let me say that getPageIdentity() is indeed better.
Thank you. I would like to continue investigating some ideas, though,
so please bear with me...
On Wed, 26 Jan 2005 13:17:24 -0800, Jonathan Locke wrote:
>stop and think about this for a minute. if you instantiate the page
>you're linking to, all *its* links would have to instantiate *their*
>pages... and so on... for most sites, you would wind up instantiating
>every page on the site since they are all connected. delayed linking is
>a core design of wicket and is not something that will ever go away.
I am asking for delayed linking to go away. I am simply saying
we should investigate going further with lazy loading.
Why not defer adding children (such a links) to a Page until
render-time? I mean, right now we add() in the constructor of a Page
whereas we could separate Page construction and Page configuration.
You'd invoke Page.init() -- or whatever you decide on calling it -- the
first time a page gets rendered. This way you wouldn't end up
populating parts of the model unless needed. This would benefit
IPageLink and perhaps other mechanisms in the future that want to get
at model information without actually rendering the whole thing. It
might also help reduce memory usage.
Gili
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
