anchor.diff:  
   * improved: add support for timestamps as parameter for constructor of xmlrpcval
   
  -* improved: add option `dates_as_objects` to php_xmlrpc_decode to return dateTime objects for xmlrpc datetimes
  +* improved: add option `dates_as_objects` to `php_xmlrpc_decode` to return dateTime objects for xmlrpc datetimes
   
   * improved: add new method `SetCurlOptions` to xmrlpc_client to allow extra flexibility in tweaking http config, such as
       explicitly binding to an ip address
  
positive.code:     which, strictly speaking, breaks the xml-rpc spec. Other xmlrpc implementations are supposed to ignore such an
      attribute (unless they implement a brain-dead custom xml parser...), so it should be safe enabling it in
      heterogeneous environments. The activation of this feature is done by usage of an option passed as second parameter
      to both ++$$php_xmlrpc_encode$$++ and ++$$php_xmlrpc_decode$$++.
  
  * Extend the ++$$php_xmlrpc_encode$$++ function to allow automatic serialization of iso8601-conforming php strings as
      datetime.iso8601 xmlrpcvals, by usage of an optional parameter
  
  * Added an automatic stub code generator for converting xmlrpc methods to php functions and vice-versa.
  +
  This is done via two new functions: ++$$wrap_php_function$$++ and ++$$wrap_xmlrpc_method$$++, and has many caveats,
      with php being a typeless language and all...
  
  * Allow object methods to be used in server dispatch map
  
  * Added a complete debugger solution, in the __debugger__ folder
  
  * Added configurable server-side debug messages, controlled by the new method ++$$xmlrpc_server::SetDebug()$$++.
      At level 0, no debug messages are sent to the client; level 1 is the same as the old behaviour; at level 2 a lot
      more info is echoed back to the client, regarding the received call; at level 3 all warnings raised during server
      processing are trapped (this prevents breaking the xml to be echoed back to the client) and added to the debug info
  
negative.code: * let server and client objects serialize calls using a specified character set encoding for the produced xml instead of
      US-ASCII (ISO-8859-1 and UTF-8 supported)
  
  * let `php_xmlrpc_decode` accept xmlrpcmsg objects as valid input
  
  * 'class::method' syntax is now accepted in the server dispatch map
  
  * `xmlrpc_clent::SetDebug()` accepts integer values instead of a boolean value, with debugging level 2 adding to the
      information printed to screen the complete client request
  
  === 2.0 Release candidate 2
  
  * Added a new property of the client object: `xmlrpc_client->return_type`, indicating whether calls to the
      send() method will return xmlrpcresp objects whose value() is an xmlrpcval object, a php value (automatically
      decoded) or the raw xml received from the server.
  
  * Added in the extras dir. two new library files: _jsonrpc.inc_ and _jsonrpcs.inc_ containing new classes that
      implement support for the json-rpc protocol (alpha quality code)
  
  * Added a new client method: `setKey($key, $keypass)` to be used in HTTPS connections
  
  * Added a new file containing some benchmarks in the testsuite directory
  
  === 2.0 Release candidate 1
  
  * Support for HTTP proxies (new method: `xmlrpc_client::setProxy()`)
  
  * Support HTTP compression of both requests and responses.
      Clients can specify what kind of compression they accept for responses between deflate/gzip/any, and whether to
      compress the requests.
      Servers by default compress responses to clients that explicitly declare support for compression (new methods:
      `xmlrpc_client::setAcceptedCompression()`, `xmlrpc_client::setRequestCompression()`).
      Note that the ZLIB php extension needs to be enabled in PHP to support compression.
  
  * Implement HTTP 1.1 connections, but only if CURL is enabled (added an extra parameter to
      `xmlrpc_client::xmlrpc_client` to set the desired HTTP protocol at creation time and a new supported value for
      the last parameter of `xmlrpc_client::send`, which now can be safely omitted if it has been specified at
      creation time).
  +
  With PHP versions greater than 4.3.8 keep-alives are enabled by default for HTTP 1.1 connections. This should yield
      faster execution times when making multiple calls in sequence to the same xml-rpc server from a single client.
  
  * Introduce support for cookies.
      Cookies to be sent to the server with a request can be set using `xmlrpc_client::setCookie()`, while cookies
      received from the server are found in ++xmlrpcresp::cookies()++. It is left to the user to check for validity of
      received cookies and decide whether they apply to successive calls or not.
  
  