Changes between Initial Version and Version 1 of XMLRPC


Ignore:
Timestamp:
06/30/09 12:48:37 (8 years ago)
Author:
sander
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • XMLRPC

    v1 v1  
     1= XML-RPC =  
     2 
     3The XML-RPC API is used by [ClientFactory ClientFactories] to poll for new documents in the queue and to submit finished work back to the CentralServer. 
     4For more information about using the API to create a ClientFactory, see FactoryManual/FromScratch 
     5 
     6== XML-RPC endpoint == 
     7 
     8 production server:: 
     9    https://www.officeshots.org/xmlrpc 
     10 development server:: 
     11    https://dev.officeshots.org/xmlrpc 
     12 
     13== XML-RPC functions == 
     14 
     15 * [wiki:XMLRPC/JobsPoll jobs.poll] 
     16 * [wiki:XMLRPC/JobsFinish jobs.finish] 
     17 
     18== Authentication == 
     19 
     20Authentication is not part of the XML-RPC interface. The XML-RPC endpoint runs on an SSLv3/TLS webserver that requires client certificates for authentication. In order to use the API you will need an SSLv3/TLS client certificate signed by a trusted Certificate Authority that verifies your e-mail address. You can obtain such certificates from various Certificate Authorities such as CACert. The e-mail address on the client certificate must match the account that you registered with Office-shots. Furthermore, your account must have been granted the privilege to run a factory. See FactoryManual/Setup 
     21 
     22[[NoteBox(note, The development server uses mod_gnutls instead of mod_ssl for SSL/TLS support. This means that to use the development server your client needs to understand [http://en.wikipedia.org/wiki/Server_Name_Indication Server Name Indication]. Also, [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=511573 there is a bug in mod_gnutls] that means the development server can only accept client certificates from CACert. The production server uses mod_ssl and does not have these limitations.)]]