We do call response.encodeUrl if we don't do that then jsessionid is not inserted into the url.
But if we don't do that then sessions could be lost when a browser has cookies disabled..
johan
On 4/11/06, Nathan Hamblen <[EMAIL PROTECTED]> wrote:
Michael Day wrote:
> If not, then wicket cannot be used for public web sites (news,
> online store, etc) that need to be indexed in today's search engines.
Johan Compagner wrote:
> If you want a really stateless page/site. Then everything must be
> bookmarkable/mountable links..and you can't use our
> form components
[...]
Yes. Ample bookmarkable links are all you need for good indexing. Try
googling "British Lemon Meringue Pie" and see that the second result is
in fact a Wicket demo application.
I wouldn't worry about forms too much since Google doesn't follow them
anyway. As long as you can get to the content through bookmarkable
links, it will be indexed. The fact that a session always exists is
irrelevant and entirely normal. (Even ASP 3.0 created a session on the
"very first hit.")
My only wish is to get rid of that silly ;jsessionid=66kiemewvs53 but I
don't think that's up to Wicket.
Nathan
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
