Waarp Thrift is repository of Thrift definitions for Waarp project.
It implements a Thrift interface. It allows one to develop his own interface to one Waarp project using his own langage (according to Thrift support).
The first item is for Waarp R66.
The “usethrift” option (specifying a port > 0) allows to enable the Thrift server support in one R66 server. Currently only Synchronous Binary thrift protocol is allowed, so a client should use “Tsocket” for its Ttransport and “TbinaryProtocol” for its Tprotocol.
One example in Java is given in org.waarp.openr66.protocol.test.TestThriftClientExample to show how to interact with the Thrift R66 service.
This option should enables more capabilities to R66 to be embedded in existing applications, in a more large cover than just Java.
The current methods available are:
transferRequestQuery: allows to initiate a submitted transfer from the related R66 server to another one. Note that the request could be asynchronous (immediately returns once the request is submitted) or synchronous (returns only once the request is done, whatever in error or in success, but it does not take into account future reschedule if any as it will return the status once the current try is over).
InfoTransferQuery: allows to request some information on one particular transfer request
isStillRunning: allows to quickly have the information on one particular transfer request running status or not
infoListQuery: allows to get the information on file list on the local R66 server
Note that the Thrift service, for security reason, is only opened on 127.0.0.1 address since no authentication is made, as it stands for a local service.