[
https://issues.apache.org/jira/browse/TIKA-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14362467#comment-14362467
]
Sergey Beryozkin commented on TIKA-891:
---------------------------------------
What I do feel rather strongly about is that the existing users should not
start seeing the client code expecting PUT supported breaking.
The duplication is usually of some concern to developers initially but always
proves to be negligible in terms of what actually (how much) is duplicated.
Some people can do a ContainerRequestFilter that will adapt PUT requests to
POST and save a bit on typing duplicate method definitions though at a minor
extra cost of having to maintain yet another provider.
> 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.9
>
>
> 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)
