X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=doc%2Fmanual%2Fphpxmlrpc_manual.adoc;h=97f5ccd1a46f6a1974c35eb0f75ade094992b844;hb=3b18a711d68f936d7395ade1903fe0875cb5fd9c;hp=50af655ae030e4fef1151e6fc503fb7ec41a6582;hpb=5fc0c8cc5cc3d0579e0e810512ca3b672e720db6;p=plcapi.git

diff --git a/doc/manual/phpxmlrpc_manual.adoc b/doc/manual/phpxmlrpc_manual.adoc
index 50af655..97f5ccd 100644
--- a/doc/manual/phpxmlrpc_manual.adoc
+++ b/doc/manual/phpxmlrpc_manual.adoc
@@ -133,14 +133,8 @@ demo/*:: example code for implementing both xmlrpc client and server functionali
 
 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
@@ -220,12 +214,16 @@ If you've benefited from the effort that has been put into writing this software
 
 ===== int
 
-The type i4 and i8 are accepted as a synonym
+The type i4 is accepted as a synonym
           for int when creating xmlrpcval objects. The
-          xml parsing code will always convert i4 and i8 to
+          xml parsing code will always convert i4 to
           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
@@ -1680,7 +1678,7 @@ The most likely cause is that you are not using the correct URL
 
 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?