<bookinfo>
<date>June 15, 2014</date>
+
<authorgroup>
<author>
<firstname>Edd</firstname>
</itemizedlist></para>
</sect1>
- <sect1> <title>3.0.0 beta</title>
+ <sect1>
+ <title>3.0.0 beta</title>
<para>This is the first release of the library to only support PHP 5.
Some legacy code has been removed, and support for features such as
<para>The <function>wrap_php_function</function> and
<function>wrap_xmlrpc_method</function> functions have been moved
out of the base library file <filename>xmlrpc.inc</filename> into
- a file of their own: <filename>xmlrpc_wrappers.inc</filename>. You
+ a file of their own: <filename>xmlrpc_wrappers.php</filename>. You
will have to include() / require() it in your scripts if you have
been using those functions. For increased security, the automatic
rebuilding of php object instances out of received xmlrpc structs
</glossentry>
<glossentry>
- <glossterm>lib/xmlrpc_wrappers.inc</glossterm>
+ <glossterm>lib/xmlrpc_wrappers.php</glossterm>
<glossdef>
<para>helper functions to "automagically" convert plain php
</glossentry>
<glossentry>
- <glossterm>demo/demo1.txt, demo/demo2.txt, demo/demo3.txt</glossterm>
+ <glossterm>demo/demo1.xml, demo/demo2.xml, demo/demo3.xml</glossterm>
<glossdef>
<para>XML-RPC responses captured in a file for testing purposes (you
<para>Examples:</para>
<programlisting language="php">
-$myInt = new xmlrpcvalue(1267, "int");
-$myString = new xmlrpcvalue("Hello, World!", "string");
-$myBool = new xmlrpcvalue(1, "boolean");
-$myString2 = new xmlrpcvalue(1.24, "string"); // note: this will serialize a php float value as xmlrpc string
+$myInt = new xmlrpcval(1267, "int");
+$myString = new xmlrpcval("Hello, World!", "string");
+$myBool = new xmlrpcval(1, "boolean");
+$myString2 = new xmlrpcval(1.24, "string"); // note: this will serialize a php float value as xmlrpc string
</programlisting>
<para>The fourth constructor form can be used to compose complex
<function>parseResponse.</function></para>
<para>This method is useful to construct responses from pre-prepared
- files (see files <literal>demo1.txt, demo2.txt, demo3.txt</literal>
+ files (see files <literal>demo1.xml, demo2.xml, demo3.xml</literal>
in this distribution). It processes any HTTP headers it finds, and
does not close the file handle.</para>
</sect3>