doc/*:: the documentation/ this manual, and the list of API changes between versions 3 and 4
-extras/rsakey.pem:: A test certificate key for the SSL support, which can be used to generate dummy certificates. It has
- the passphrase "test."
-
extras/test.pl, extras/test.py:: Perl and Python programs to exercise server.php to test that some of the methods work.
-extras/workspace.testPhpServer.fttb:: Frontier scripts to exercise the demo server. Thanks to Dave Winer for permission
- to include these. See link:$$http://www.xmlrpc.com/discuss/msgReader$853$$[Dave's announcement of these.]
-
lib/*:: a compatibility layer for applications which still rely on version 3 of the API
src/*:: the XML-RPC library classes. You can autoload these via Composer, or via a dedicated Autoloader class
int: int is regarded
by this implementation as the canonical name for this type.
+The type i8 on the other hand is considered as a separate type.
+ Note that the library will never output integers as 'i8' on its own,
+ even when php is compiled in 64-bit mode.
+
===== base64
Base 64 encoding is performed transparently to the caller when
reserved for library usage.
-==== $xmlrpcI4, $xmlrpcInt, $xmlrpcBoolean, $xmlrpcDouble, $xmlrpcString, $xmlrpcDateTime, $xmlrpcBase64, $xmlrpcArray, $xmlrpcStruct, $xmlrpcValue, $xmlrpcNull
+==== $xmlrpcI4, $xmlrpcI8 $xmlrpcInt, $xmlrpcBoolean, $xmlrpcDouble, $xmlrpcString, $xmlrpcDateTime, $xmlrpcBase64, $xmlrpcArray, $xmlrpcStruct, $xmlrpcValue, $xmlrpcNull
For convenience the strings representing the XML-RPC types have
been encoded as global variables:
----
$xmlrpcI4="i4";
+$xmlrpcI8="i8";
$xmlrpcInt="int";
$xmlrpcBoolean="boolean";
$xmlrpcDouble="double";
To find out what the server is really returning to your client,
you have to enable the debug mode of the client, using
- $client->setdebug(1);
+ $client->setDebug(1);
==== How can I save to a file the xml of the xmlrpc responses received from servers?