Well, people can still argue whether it is in Google's way or not. See my comment at http://technically.us/n8/articles/2006/05/07/baking-for-google#comments
A session will still be created, even if you only have bookmarkable pages. We tried to get rid of it, but it prooved undoable at this time. If you have bookmarkable pages without any callbacks (like internal links and forms etc) on them, they won't be stored in the session. You can achieve 'near statelessness' by coding all your bookmarkable pages like that, only use links to other bookmarkable pages (or to the same but as a bookmarkable link using parameters). However, if you plan to code your whole application like that, you should consider whether Wicket is the right framework for you, as having stateful components is the big idea of the framework. Eelco On 6/7/06, John Patterson <[EMAIL PROTECTED]> wrote: > Hi, > > I was wondering what the current state of wicket is regarding not > adding a JSESSIONID to pages served to search engine bots? Also, are > http sessions still created if I use only bookmarkable pages and > don't want to store any application session state? > > Thanks, > > John. > > > > _______________________________________________ > Wicket-user mailing list > Wicket-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wicket-user > _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
