[
https://issues.apache.org/jira/browse/TIKA-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12837750#action_12837750
]
Ingo Renner commented on TIKA-169:
----------------------------------
I see a servlet making quite some sense - think of Solr, but only having the
extraction request handler... That way you could have a central meta data /
text extracting server without needing to install java + tika on all the hosts
where you might need it in a replicated CMS environment f.e.
So the scenario would be that a CMS trys to extract text, meta data from a
file, but does not have a local tika at hand. It would then send the file to a
Tika server and get the results back in XML or JSON like Solr does.
> Tika Web Service Servlet
> ------------------------
>
> Key: TIKA-169
> URL: https://issues.apache.org/jira/browse/TIKA-169
> Project: Tika
> Issue Type: New Feature
> Components: general
> Affects Versions: 0.2
> Reporter: Rida Benjelloun
> Priority: Minor
> Attachments: tikaServlet.war
>
>
> Tika servlet, use file or directory path to build a list of XML documents.
> The next version will allow file upload.
> Usage :
> //Extract document content and metadata
> http://localhost:8080/tikaServlet/?filePath=C:\test&start=0&rows=10
> //Extract metadata
> http://localhost:8080/tikaServlet/?filePath=C:\test&start=0&rows=10&extract=metadata
> //Extract document content
> http://localhost:8080/tikaServlet/?filePath=C:\test&start=0&rows=10&extract=content
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
