All my pages which should be indexed by bots require no "conversation" state to be storedand would all be bookmarkable. Would it be possible to have common pages (or page components) stored in the application scope instead? They could then have their rendered content cached too.
i dont think so, components like that dont really make sense and in 2.0 they have to be added to the parent on instantiation with the constructor refactor. if you want to cache output you can implement that yourself.
It would be really great if it could be solved. I remember Jonathon Locke talking about Wicket 1.0 on TSS and saying "Client side state, including zero-state will be available in 1.1. " That statement was one of the reasons I chose to start developing in wicket. Now I find I have to maintain two separate frameworks for different parts of my site.
well, we made an attempt in 1.2 to hold off session creation until a stateful page was hit, but it turned out too hard. i think we will try again in 2.0, maybe johan and eelco can elaborate more.
Currently, I am considering either apache url rewriting to remove all session ids from non-conversational pages or hacking wicket to disable url encoding for all pages that do not absolutely require a session.
yeah, as long as the pages are all bookmarkable and their urls are stable.
Any comments on these approaches? Is there any thing currently in wicket that would help me selectively disable url encoding?
check out nathan hamblen's blog, he blogs about disabling url rewriting from wicket's end and the code is in the databinder project.
-Igor
_______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
