You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Maxim Valyanskiy (JIRA)" <ji...@apache.org> on 2011/02/08 09:51:57 UTC

[jira] Commented: (TIKA-593) Tika network server

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

Maxim Valyanskiy commented on TIKA-593:
---------------------------------------

I made HTTP-server with Jersey (JAX-RS) and embedded Glassfish (or Grizzly?) for text, metadata and binary attachment extraction.  I has very simple REST-style interface

I think we can contribute it to Tika project. Also I can try to replace Glassfish and Jersey with Tomcat and Apache Wink if it is required.

What do you think?

> Tika network server
> -------------------
>
>                 Key: TIKA-593
>                 URL: https://issues.apache.org/jira/browse/TIKA-593
>             Project: Tika
>          Issue Type: New Feature
>          Components: general
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>
> It would be cool to be able to run Tika as a network service that accepts a binary document as input and produces the extracted content (as XHTML, text, or just metadata) as output. A bit like TIKA-169, but without the dependency to a servlet container.
> I'd like to be able to set up and run such a server like this:
>     $ java -jar tika-app.jar --port 1234
> We should also add a NetworkParser class that acts as a local client for such a service. This way a lightweight client could use the full set of Tika parsing functionality even with just the tika-core jar within its classpath.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira