tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Palsulich (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TIKA-891) Use POST in addition to PUT on method calls in tika-server
Date Mon, 02 Mar 2015 22:16:06 GMT

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

Tyler Palsulich commented on TIKA-891:

I was mistaken when I said there are only 3 PUT resources in the server:
➜  tika-server  grep -RA 4 "@PUT" . | grep public | cut -d'(' -f1
./src/main/java/org/apache/tika/server/DetectorResource.java-    public String detect
./src/main/java/org/apache/tika/server/MetadataResource.java-    public Response getMetadata
./src/main/java/org/apache/tika/server/MetadataResource.java-    public Response getMetadataField
./src/main/java/org/apache/tika/server/RecursiveMetadataResource.java-    public Response
./src/main/java/org/apache/tika/server/TikaResource.java-    public StreamingOutput getText
./src/main/java/org/apache/tika/server/TikaResource.java-    public StreamingOutput getHTML
./src/main/java/org/apache/tika/server/TikaResource.java-    public StreamingOutput getXML
./src/main/java/org/apache/tika/server/UnpackerResource.java-    public Map<String, byte[]>
./src/main/java/org/apache/tika/server/UnpackerResource.java-    public Map<String, byte[]>

What do you think of the rest of these, [~sergey_beryozkin]?

> 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
> {code}
> {code}
> annotations to the methods we are currently exposing using PUT to take care of this.

This message was sent by Atlassian JIRA

View raw message