Johan Compagner wrote: > defering the creation of the session and the whole google crawler thing > are 2 seperate issues for me. > > Because a bookmarkable url could be a non stateless page anyway because > of a form or link on it. > And then you do have the session. And urls with jsessionid will be > generated after that for every > page, bookmarkable mountable or whatever, that is hit after that.
Yes, exactly! There may be other reasons to defer the session creation, but it will not fix this problem of Google finding perfectly accessible bookmarkable pages with a jsesionid appended to them, unless your robots.txt is able to exclude everything but bookmarkable links. Could we do that? It might be the best of all worlds. Until then, though, (and I don't think that needs to go in to 1.2) turning off rewriting is a perfectly good "workaround." It's not like other web app technologies have a better solution to this problem. They either won't give cookieless people a session or they abandon that session when the user browses back into static-URL land. (Or they bind to the IP? That's nuts though.) If we're able to generate (at runtime?) a robots.txt that guides a search engine through bookmarkable pages that don't open a session, we'd have a far better implementation than everyone else. 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 [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
