[ 
https://issues.apache.org/jira/browse/TIKA-2558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Sveen updated TIKA-2558:
-------------------------------
    Description: 
Using Tika with Mono on Windows, Linux and Mac I miss a simple and 
OS-independent way to get the Process ID of a running Tika service. 

Therefore, I suggest that the following API is added  to Tika:

*GET* _[/pid|http://localhost:16200/version]_
 Class: org.apache.tika.server.resource.TikaPID (guessing that this would be 
the class)
 Method: getPID
 Produces: text/plain

The output would be the integer value (as a string) of the PID

 

  was:
Using Tika with Mono on Windows, Linux and Mac I miss a simple and 
OS-independent way to get the Process ID of a running Tika service. 

Therefore, I suggest that the following API is added  to Tika:

*GET* _[/pid|http://localhost:16200/version]_
 Class: org.apache.tika.server.resource.TikaPID (guessing that this would be 
the class)
 Method: getPID
 Produces: text/plain

The output would the integer value (as a string) of the PID

 


> Add a new pid api to Tika
> -------------------------
>
>                 Key: TIKA-2558
>                 URL: https://issues.apache.org/jira/browse/TIKA-2558
>             Project: Tika
>          Issue Type: New Feature
>          Components: general
>    Affects Versions: 1.17
>         Environment: All platforms on which Tika can run.
>            Reporter: Stefan Sveen
>            Priority: Minor
>             Fix For: 1.18
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Using Tika with Mono on Windows, Linux and Mac I miss a simple and 
> OS-independent way to get the Process ID of a running Tika service. 
> Therefore, I suggest that the following API is added  to Tika:
> *GET* _[/pid|http://localhost:16200/version]_
>  Class: org.apache.tika.server.resource.TikaPID (guessing that this would be 
> the class)
>  Method: getPID
>  Produces: text/plain
> The output would be the integer value (as a string) of the PID
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to