Difference between revisions of "Apertium services"

From Apertium
Jump to navigation Jump to search
Line 1: Line 1:
 
There are three main Apertium service implementations:
 
There are three main Apertium service implementations:
   
* <code>apertium-service</code>, see [[Apertium-service]] (its development was documented here: [[Apertium going SOA]])
+
* <code>apertium-service</code>, see [[Apertium-service]], a multithreaded C++ XML-RPC/REST/SOAP server, using apertium as a library
   
* <code>ScaleMT</code>, see [[ScaleMT]]
+
* <code>ScaleMT</code>, see [[ScaleMT]], a multiprocess Java XML-RPC/REST server, starting apertium language pairs as new processes
   
* <code>apertium-apy</code>, see [[apy]], a Python 3 tornado http server
+
* <code>apertium-apy</code>, see [[apy]], a multiprocess Python 3 tornado http server, starting apertium language pairs as new processes
   
 
You can download the source code of these services and install any of them on your own server, or use the [[Apertium web service]], which is based on [[ScaleMT]] and is installed on our servers.
 
You can download the source code of these services and install any of them on your own server, or use the [[Apertium web service]], which is based on [[ScaleMT]] and is installed on our servers.

Revision as of 09:25, 16 January 2014

There are three main Apertium service implementations:

  • apertium-service, see Apertium-service, a multithreaded C++ XML-RPC/REST/SOAP server, using apertium as a library
  • ScaleMT, see ScaleMT, a multiprocess Java XML-RPC/REST server, starting apertium language pairs as new processes
  • apertium-apy, see apy, a multiprocess Python 3 tornado http server, starting apertium language pairs as new processes

You can download the source code of these services and install any of them on your own server, or use the Apertium web service, which is based on ScaleMT and is installed on our servers.


Applications which use the Apertium service include Virtaal, Okapi, OmegaT, begiak, …


See also