Exactly. That's a half baked solution at best. And though unlikely a real problem, I wouldn't want to have to depend on the user-agent the client sends. The solution we have got now - stateless pages (and you can actually use forms on them like you would normally do, except for the fact that any state you don't send with the form is disregarded) - combined with defering session creation really is the best. It gives you the same characteristics of model 2 applications in terms of scalability and crawlability (is that a word?).
Eelco On 6/14/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > wicket 1.2.x and earlier create a session on first request so this approach > would mean a new session created from every hit from the spider. something > to consider. > > -Igor > > > > On 6/14/06, Aaron Metzger <[EMAIL PROTECTED]> wrote: > > John Patterson wrote: > > > On 13 Jun 2006, at 19:55, Eelco Hillenius wrote: > > > > > >> Or maybe there will be more trade offs. Depends on how badly people > > >> want it, and who will work on it. In 2.0, Johan built in a form that > > >> posts back to a bookmarkable page, so you can even build pages with > > >> forms that are still stateless. > > > > > > > > They are having the same discussion over on the Tapestry list. > > Someone answered: > > > > >> > You can prevent JSESSIONID from being encoded onto URLs for bots. At > > > Zillow, we've done this with a ServletFilter that compares the incoming > > > user agent to a list of known bots, and if it matches replaces the > > > HttpServletResponse with an HttpServletResponseWrapper that makes the > > > encodeURL, encodeUrl, encodeRedirectURL, and encodeRedirectUrl methods > > > into no-ops (simply returning their inputs). > > > > > > > > > > > > > > > > > >> Eelco > > >> > > > > > > OK, thanks I will have a look into that. I have not yet checked out > > > 2.0 but would you just be able to clarify - when a stateless form is > > > submitted would I still use an onClick handler on my form component? > > > Or do I need to work with page parameters and move my form processing > > > logic away from the actual form component? > > > > > > > > > _______________________________________________ > > > 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 > > > > > > > _______________________________________________ > 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
