[ 
https://issues.apache.org/jira/browse/TIKA-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343816#comment-14343816
 ] 

Sergey Beryozkin edited comment on TIKA-891 at 3/2/15 9:44 PM:
---------------------------------------------------------------

If I said PUT was the same as POST then I'd probably be seriously criticized at 
the very least :-). My point was, that neither verb is probably that 
semantically close for the type of the action Tika Server supports. Typically I 
prefer just to get things done though risking sometimes writing a possibly not 
very pure REST code :-). However you are right forms do not support PUT hence I 
guess I'd be better to have POST across the board for the sake of consistency. 
And if you agree - then keeping PUT for 1.8 as deprecated and removing in 1.9

Sergey


was (Author: sergey_beryozkin):
If I said PUT was the same as POST I'd be probably seriously criticized at the 
very least :-). My point was, that neither verb is probably not that 
semantically close for the type of the action Tika Server supports. Typically I 
prefer just to get things done though risking sometimes writing a possibly not 
very pure REST code :-). However you are rights forms do not support PUT hence 
I guess I'd be better to have POST across the board for the sake of 
consistency. And if you agree - then keeping PUT for 1.8 as deprecated and 
removing in 1.9

Sergey

> Use POST in addition to PUT on method calls in tika-server
> ----------------------------------------------------------
>
>                 Key: TIKA-891
>                 URL: https://issues.apache.org/jira/browse/TIKA-891
>             Project: Tika
>          Issue Type: Improvement
>          Components: general
>            Reporter: Chris A. Mattmann
>            Assignee: Chris A. Mattmann
>            Priority: Trivial
>              Labels: newbie
>             Fix For: 1.8
>
>
> Per Jukka's email:
> http://s.apache.org/uR
> It would be a better use of REST/HTTP "verbs" to use POST to put content to a 
> resource where we don't intend to store that content (which is the 
> implication of PUT). Max suggested adding:
> {code}
> @POST
> {code}
> annotations to the methods we are currently exposing using PUT to take care 
> of this. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to