[
https://issues.apache.org/jira/browse/TIKA-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14342977#comment-14342977
]
Sergey Beryozkin commented on TIKA-891:
---------------------------------------
IMHO it might make sense to keep PUT as deprecated for the next release so that
the existing users can still get it working and provide a documentation
suggesting that PUT will be removed in 1.9. Or at the very least offer such a
migration guide for 1.8
As a side note, I don't know PUT was put in the first place, but speaking of
the semantics, I'm not 100% sure POST (effectively adding a resource to the
collection) is the closest match to what Tika JAX-RS server does, by accepting
a resource and echoing its metadata/data back.
Cheers, 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)
