Nope, we do need a session for everything except a trivial page (and
from the framework to figure out whether the page is 'trivial' that
would involve some major hacking). EVERYTHING that can trigger a
'postback', be it forms, links or whatever, needs that page to be in the
session.
It might be a feature request for our next version (1.2 that is) when we
tackle the whole stateless page thing (if we ever tackle that
succesfully, as currently the disadvantages seem to be greater than the
very few advantages it would get you... but that's another discussion
for some other time). But for 1.0.1/ 1.1, we can't change it.
Eelco
Gili wrote:
First, I like the new setPageAlias() functionality :)
I still don't understand however why one needs to store the Page
component ID on the session (at least for bookmarkable pages the first
time they are hit). Also, Eelco previously mentioned that jsessionid
is only showing up because we're creating a session. My point is, we
*shouldn't* be creating a session for bookmarkable pages unless for
example the page contains a form, and someone submits it. We should be
creating session on-demand, not right away. Maybe once I understand
more about why we need path=X, this will make more sense.
Thanks,
Gili
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
