[jira] Commented: (TAP5-1285) Allow GET method in form component

["Lutz Hühnken (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TAP5-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12919475#action_12919475 ] 

Lutz Hühnken commented on TAP5-1285:
------------------------------------

Well, this fairly large block of data... this would be quite the drawback. For me, at least. As one advantage of the GET request I would see the simplicity and bookmarkability of the resulting URL, such as /search?q=tapestry.

Maybe my idea wasn't so good and rather than supporting GET in the existing Tapestry from element, the better approach would be to use/create a separate component that renders a "GET" form, and not much else.



> Allow GET method in form component
> ----------------------------------
>
>                 Key: TAP5-1285
>                 URL: https://issues.apache.org/jira/browse/TAP5-1285
>             Project: Tapestry 5
>          Issue Type: Wish
>          Components: tapestry-core
>            Reporter: Lutz Hühnken
>            Priority: Minor
>
> The Tapestry form component is currently only supporting the "POST" method.
> The POST method is usually associated with changing the "model" on the server side, e.g. in REST applications, POST indicates that a resource is modified, if I am not mistaken.
> The lack of GET support makes it necessary to use POST also for simple queries, such as a search field, where the model is not modified.
> This is a) semantically irritating, since for example a search query will not modify state and
> b) requires extra "work", for example a redirect-after-post, where it should not be necessary.
> Since Tapestry aspires to make the simple things easy, the difficult things possible, I think it should provide first-class support for the GET method.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.