The 'extras' library is formed by many separate components, grouped together for ease of download. The terms 'component' and package' are used interchangeably within this manual to indicate groups of files that provide a particular capability. Please note that the term 'package' is used with a different meaning on the library download pages on the www.sourceforge.net website, where the complete extras collection is in fact called a package in itself.
Included packages as of the current release are:
ADODB: designed to provide a flexible and easy-to-use database-to-webservice conversion mechanism. Based on the adodb library by John Lim, it includes conversion functions, server component and meta-db-driver that allows transparent access to remote databases over http.
AJAX: demo of an ajaxified version of the php-xmlrpc lib: supports executing xmlrpc/jsonrpc calls directly from the client browser. Needs the excellent jsolait lib from http://jsolait.net/ (thanks Jan Kollhof) or the jsxmlrpc lib.
DOCXMLRPCS: subclass of xmlrpc server that auto-generates HTML documentation of exposed services. Easy as a breeze to use, and extremely user-friendly (it is used on the main php-xmlrpc website, too).
JSONRPC: support for this brand new protocol, 100% buzzword-compliant and ajax-ready. Client and server classes provided. Makes it very easy to build a server that supports both xmlrpc and jsonrpc protocols at the same time. The original JSON parsing code was from Michal Migurski (whose lib is now officially part of PEAR).
PROXY: subclass of xmlrpc server that can act as remote (transparent) xmlrpc proxy to forward calls to a remote server. Can either forward any received call or probe the remote server first for existing methods.
WSDL: the completely UNOFFICIAL DTD and RELAX NG schemas to validate your xmlrpc against. Might be useful in defining some wsdl file describing xmlrpc services (good luck!!!). The DTD is not quite accurate, due to inherent limitations in the definition language. The RELAX NG schema should be on the other hand 100% precise and accurate.
XMLRPC_EXTENSION_API: a replacement for the php native xmlrpc extension, written in 100% pure php. Typical use case: enabling a php application, written taking advantage of the php native xmlrpc extension, to run also on webservers where the extension is not / can not be installed.