Difference between revisions of "Example Clients"
(→Example Clients for Retrieving Results of Batch Requests) |
|||
| (14 intermediate revisions by the same user not shown) | |||
| Line 16: | Line 16: | ||
== Example Clients for Interactive Jobs == | == Example Clients for Interactive Jobs == | ||
| − | Below there is a list of example of how to | + | Below there is a list of example of how to send an interactive request to a service named <tt>SERVICENAME</tt> using different programming languages. |
| − | You'll need to replace <tt>SERVICENAME</tt> with the actual name of the desired service, and adapt the list of parameters in the | + | You'll need to replace <tt>SERVICENAME</tt> with the actual name of the desired service, and adapt the list of parameters in the request to those expected by the service. |
| − | * '''[[ | + | * '''[[Python2 Interactive Client|Python2]]''' |
| + | * '''[[Python3 Interactive Client|Python3]]''' | ||
* '''[[Java Interactive Client|Java]]''' | * '''[[Java Interactive Client|Java]]''' | ||
* '''[[Perl Interactive Client|Perl]]''' | * '''[[Perl Interactive Client|Perl]]''' | ||
* '''[[PHP Interactive Client|PHP]]''' | * '''[[PHP Interactive Client|PHP]]''' | ||
| − | * '''[[curl Interactive Client|curl]]''' | + | * '''[[curl Interactive Client|bash (using curl)]]''' |
== Example Clients for Batch Jobs == | == Example Clients for Batch Jobs == | ||
| − | Below there is a list of example of how to | + | Below there is a list of example of how to send a batch request to a service named <tt>SERVICENAME</tt> using different programming languages. |
You'll need to replace <tt>SERVICENAME</tt> with the actual name of the desired service, and adapt the list of parameters in the multipart form to those expected by the service. | You'll need to replace <tt>SERVICENAME</tt> with the actual name of the desired service, and adapt the list of parameters in the multipart form to those expected by the service. | ||
| − | These clients send the request and | + | These clients send the request and obtain the job Token ID from TextServer. This Token ID can be used later to retrieve the results of the job |
| − | * '''[[ | + | * '''[[Python2 Batch Client|Python2]]''' |
| + | * '''[[Python3 Batch Client|Python3]]''' | ||
* '''[[Java Batch Client|Java]]''' | * '''[[Java Batch Client|Java]]''' | ||
* '''[[Perl Batch Client|Perl]]''' | * '''[[Perl Batch Client|Perl]]''' | ||
* '''[[PHP Batch Client|PHP]]''' | * '''[[PHP Batch Client|PHP]]''' | ||
| − | * '''[[curl Batch Client|curl]]''' | + | * '''[[curl Batch Client|bash (using curl)]]''' |
| + | |||
| + | == Example Clients for Retrieving Results of Batch Requests == | ||
| + | |||
| + | Below there is a list of examples of how to retrieve the result of a batch job from a remote client. | ||
| + | The client just needs the username and the job Token ID to get the results. | ||
| + | |||
| + | * '''[[Batch Results Retrieval in Python2|Python2]]''' | ||
| + | * '''[[Batch Results Retrieval in Python3|Python3]]''' | ||
| + | * '''[[Batch Results Retrieval in Java|Java]]''' | ||
| + | * '''[[Batch Results Retrieval in Perl|Perl]]''' | ||
| + | * '''[[Batch Results Retrieval in PHP|PHP]]''' | ||
| + | * '''[[Batch Results Retrieval in curl|bash (using curl)]]''' | ||
Latest revision as of 10:29, 24 August 2018
To call a TextServer service from a client program running on your side, this client needs to send the appropriate request in the right format.
The request is a standard HTTP POST request with a multiform part containing the same information you would submit via the web interface.
Below you'll find a list of example client programs in different programming languages.
The same code can be used to access any TextServer service with small variations:
- Simply change the service name in the URL to access a different service. You can find out the service name at the top of the "Execute" form of your subscribed services.
- Replace the parameters in the example client with the parametes that the called service requires. Rules are simple:
- Language identification service does not require a "language" parameter, but the other services do.
- All services require a "interactive" parameter stating whether the job is interactive or batch.
- All services require either a "text_input" parameter (for interactive jobs) or a "input_file" parameter (for batch jobs).
- You can find out the name of any other specific parameters for a service in the "Execute" form of your subscribed services.
Example Clients for Interactive Jobs
Below there is a list of example of how to send an interactive request to a service named SERVICENAME using different programming languages. You'll need to replace SERVICENAME with the actual name of the desired service, and adapt the list of parameters in the request to those expected by the service.
Example Clients for Batch Jobs
Below there is a list of example of how to send a batch request to a service named SERVICENAME using different programming languages. You'll need to replace SERVICENAME with the actual name of the desired service, and adapt the list of parameters in the multipart form to those expected by the service.
These clients send the request and obtain the job Token ID from TextServer. This Token ID can be used later to retrieve the results of the job
Example Clients for Retrieving Results of Batch Requests
Below there is a list of examples of how to retrieve the result of a batch job from a remote client. The client just needs the username and the job Token ID to get the results.
