Dear Thiago, thanks for your patient reply and the advice. Of course I realize that I can still implement a search with Tapestry, with redirect-after-post or else, and I have actually done so in the past.
But please take a minute and think about these two things: 1. You say, > GET was always meant to be used in request that don't change the state of > the application (including database) and this is exactly what I would like to use it for - as I said, a search. You could re-phrase your argument: "POST was meant for requests that do change the state." So why do I have to use it for requests that do not? 2. Of course, a lot of things are doable, change the DOM and what not. But wasn't the idea of Tapestry "make the simple things easy, the difficult things possible"? A form with method=get is totally valid HTML, and I think it should be easy, not complicated. These two reasons are why I said the lack of get-forms is "puzzling" me, it just seems somewhat inconsistent with the rest of Tapestry (which I use and will continue to use with great pleasure). I did as you told me and created a JIRA ticket (a "wish") for it: "https://issues.apache.org/jira/browse/TAP5-1285"; Keep up the good work, Lutz -- altocon GmbH http://www.altocon.de/ Software Development, Consulting Hamburg, Germany --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
