I think that maybe stateless page should be always accessed by
bookmarkable url. The only difference between stateless page and regular
(bookmarkable) page would be that stateless page will not be put in the
pagemap.
But I don't know about setResponsePage. Maybe if
setResponsePage(StatelessPage page) was called, the redirect url should
be bookmarkable.
-Matej
Johan Compagner wrote:
When is a page stateless?
At first we thought when there are no callbacks (not urlFor()) calls
That is working nice. Except in a redirect strategy (the redirect to
buffer works the first time but that is more by accident.... the other
redirect fails immediantly)
So i currently have no idea how we every could have true stateless
pages. Because of the redirects and refresh/reload button in a browser.
What we could do in the case a redirect is done. Is store the pure
output in the session pagestack and not all the components/models.. so
purely the string or something else.
johan
On 2/6/06, *Jesse Sightler* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Just IMO, but I'd rather see 1.2 delayed than to see this feature
dropped completely. I think true stateless pages are one of the
biggest advancements in 1.2.
On 2/5/06, * Igor Vaynberg* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
unless we can make it work properly in the 1.2 time frame im +1
for removing it completely.
-Igor
On 2/5/06, *Johan Compagner* < [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
i already mentioned this (the error page does go to page
expired page when you refresh it)
This is just a problem. If we redirect to a page then the
page can also not be stateless.. I have currently know idea
how to fix that.
And this means that just about all pages must be in the
pagemap (so they are seen statefull)
Or we have to see if we can "recreate" the page when it is
requested. So we don't store the full page but just the data
that can construct it again..
But that is not that easy. Just think of the exception page.
We have to keep a reference to the exception because that is
what is needed to recreate it again.
johan
On 1/29/06, *Igor Vaynberg* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
we have a problem in our stateless page implementation.
we assume the page is stateless if a urlfor is never
called on it and thus there are no links leading back to
it. this is very crafty and works great. what we did not
think about is how the page is accessed, ie the url of
the page. it is possible to get access to a stateless
page under a ?path=x url. if you hit the refresh button
you will get a page expired error because the url is
pointing to a pagemap entry that was never put in to the
pagemap since the page is stateless.
i have currently disabled the support for stateless
pages. see PageMap.put(Page).
see bug 1417826 for instructions on how to reproduce the
error.
-Igor
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Wicket-develop mailing list
Wicket-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-develop
