PageRenderTime 24ms CodeModel.GetById 25ms RepoModel.GetById 7ms app.codeStats 0ms

/cpulogger-server/public_html/xmlrpc/doc/ch02s09.html

https://gitlab.com/komputer007123/cpulogger
HTML | 78 lines | 78 code | 0 blank | 0 comment | 0 complexity | 9a3648cf8ec3baa5ae331cfb7b0ceb06 MD5 | raw file
    

  1. <?xml version="1.0" encoding="UTF-8" standalone="no"?>
    2. 

  2. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    3. 

  3. <html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.0 Release candidate 1</title><link rel="stylesheet" href="xmlrpc.css" type="text/css" /><meta name="generator" content="DocBook XSL Stylesheets V1.74.3" /><link rel="home" href="index.html" title="XML-RPC for PHP" /><link rel="up" href="ch02.html" title="Chapter 2. What's new" /><link rel="prev" href="ch02s08.html" title="2.0 Release candidate 2" /><link rel="next" href="ch03.html" title="Chapter 3. System Requirements" /></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.0 Release candidate 1</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch02s08.html">Prev</a> </td><th width="60%" align="center">Chapter 2. What's new</th><td width="20%" align="right"> <a accesskey="n" href="ch03.html">Next</a></td></tr></table><hr /></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="id931426"></a>2.0 Release candidate 1</h2></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>Support for HTTP proxies (new method:
    4. 

  4.           <code class="code">xmlrpc_client::setProxy()</code>)</p></li><li><p>Support HTTP compression of both requests and responses.
    5. 

  5.           Clients can specify what kind of compression they accept for
    6. 

  6.           responses between deflate/gzip/any, and whether to compress the
    7. 

  7.           requests. Servers by default compress responses to clients that
    8. 

  8.           explicitly declare support for compression (new methods:
    9. 

  9.           <code class="code">xmlrpc_client::setAcceptedCompression()</code>,
    10. 

  10.           <code class="code">xmlrpc_client::setRequestCompression()</code>). Note that the
    11. 

  11.           ZLIB php extension needs to be enabled in PHP to support
    12. 

  12.           compression.</p></li><li><p>Implement HTTP 1.1 connections, but only if CURL is enabled
    13. 

  13.           (added an extra parameter to
    14. 

  14.           <code class="code">xmlrpc_client::xmlrpc_client</code> to set the desired HTTP
    15. 

  15.           protocol at creation time and a new supported value for the last
    16. 

  16.           parameter of <code class="code">xmlrpc_client::send</code>, which now can be
    17. 

  17.           safely omitted if it has been specified at creation time)</p><p>With PHP versions greater than 4.3.8 keep-alives are enabled
    18. 

  18.           by default for HTTP 1.1 connections. This should yield faster
    19. 

  19.           execution times when making multiple calls in sequence to the same
    20. 

  20.           xml-rpc server from a single client.</p></li><li><p>Introduce support for cookies. Cookies to be sent to the
    21. 

  21.           server with a request can be set using
    22. 

  22.           <code class="code">xmlrpc_client::setCookie()</code>, while cookies received from
    23. 

  23.           the server are found in <code class="code">xmlrpcresp::cookies()</code>. It is
    24. 

  24.           left to the user to check for validity of received cookies and
    25. 

  25.           decide whether they apply to successive calls or not.</p></li><li><p>Better support for detecting different character set encodings
    26. 

  26.           of xml-rpc requests and responses: both client and server objects
    27. 

  27.           will correctly detect the charset encoding of received xml, and use
    28. 

  28.           an appropriate xml parser.</p><p>Supported encodings are US-ASCII, UTF-8 and ISO-8859-1.</p></li><li><p>Added one new xmlrpcmsg constructor syntax, allowing usage of
    29. 

  29.           a single string with the complete URL of the target server</p></li><li><p>Convert xml-rpc boolean values into native php values instead
    30. 

  30.           of 0 and 1</p></li><li><p>Force the <code class="code">php_xmlrpc_encode</code> function to properly
    31. 

  31.           encode numerically indexed php arrays into xml-rpc arrays
    32. 

  32.           (numerically indexed php arrays always start with a key of 0 and
    33. 

  33.           increment keys by values of 1)</p></li><li><p>Prevent the <code class="code">php_xmlrpc_encode</code> function from
    34. 

  34.           further re-encoding any objects of class <code class="code">xmlrpcval</code> that
    35. 

  35.           are passed to it. This allows to call the function with arguments
    36. 

  36.           consisting of mixed php values / xmlrpcval objects.</p></li><li><p>Allow a server to NOT respond to system.* method calls
    37. 

  37.           (setting the <code class="code">$server-&gt;allow_system_funcs</code>
    38. 

  38.           property).</p></li><li><p>Implement a new xmlrpcval method to determine if a value of
    39. 

  39.           type struct has a member of a given name without having to loop
    40. 

  40.           trough all members: <code class="code">xmlrpcval::structMemExists()</code></p></li><li><p>Expand methods <code class="code">xmlrpcval::addArray</code>,
    41. 

  41.           <code class="code">addScalar</code> and <code class="code">addStruct</code> allowing extra php
    42. 

  42.           values to be added to xmlrpcval objects already formed.</p></li><li><p>Let the <code class="code">xmlrpc_client::send</code> method accept an XML
    43. 

  43.           string for sending instead of an xmlrpcmsg object, to facilitate
    44. 

  44.           debugging and integration with the php native xmlrpc
    45. 

  45.           extension</p></li><li><p>Extend the <code class="code">php_xmlrpc_encode</code> and
    46. 

  46.           <code class="code">php_xmlrpc_decode</code> functions to allow serialization and
    47. 

  47.           rebuilding of PHP objects. To successfully rebuild a serialized
    48. 

  48.           object, the object class must be defined in the deserializing end of
    49. 

  49.           the transfer. Note that object members of type resource will be
    50. 

  50.           deserialized as NULL values.</p><p>Note that his has been implemented adding a "php_class"
    51. 

  51.           attribute to xml representation of xmlrpcval of STRUCT type, which,
    52. 

  52.           strictly speaking, breaks the xml-rpc spec. Other xmlrpc
    53. 

  53.           implementations are supposed to ignore such an attribute (unless
    54. 

  54.           they implement a brain-dead custom xml parser...), so it should be
    55. 

  55.           safe enabling it in heterogeneous environments. The activation of
    56. 

  56.           this feature is done by usage of an option passed as second
    57. 

  57.           parameter to both <code class="code">php_xmlrpc_encode</code> and
    58. 

  58.           <code class="code">php_xmlrpc_decode</code>.</p></li><li><p>Extend the <code class="code">php_xmlrpc_encode</code> function to allow
    59. 

  59.           automatic serialization of iso8601-conforming php strings as
    60. 

  60.           datetime.iso8601 xmlrpcvals, by usage of an optional
    61. 

  61.           parameter</p></li><li><p>Added an automatic stub code generator for converting xmlrpc
    62. 

  62.           methods to php functions and vice-versa.</p><p>This is done via two new functions:
    63. 

  63.           <code class="code">wrap_php_function</code> and <code class="code">wrap_xmlrpc_method</code>,
    64. 

  64.           and has many caveats, with php being a typeless language and
    65. 

  65.           all...</p><p>With PHP versions lesser than 5.0.3 wrapping of php functions
    66. 

  66.           into xmlrpc methods is not supported yet.</p></li><li><p>Allow object methods to be used in server dispatch map</p></li><li><p>Added a complete debugger solution, in the
    67. 

  67.           <code class="filename">debugger</code> folder</p></li><li><p>Added configurable server-side debug messages, controlled by
    68. 

  68.           the new method <code class="code">xmlrpc_server::SetDebug()</code>. At level 0,
    69. 

  69.           no debug messages are sent to the client; level 1 is the same as the
    70. 

  70.           old behaviour; at level 2 a lot more info is echoed back to the
    71. 

  71.           client, regarding the received call; at level 3 all warnings raised
    72. 

  72.           during server processing are trapped (this prevents breaking the xml
    73. 

  73.           to be echoed back to the client) and added to the debug info sent
    74. 

  74.           back to the client</p></li><li><p>New XML parsing code, yields smaller memory footprint and
    75. 

  75.           faster execution times, not to mention complete elimination of the
    76. 

  76.           dreaded <code class="filename">eval()</code> construct, so prone to code
    77. 

  77.           injection exploits</p></li><li><p>Rewritten most of the error messages, making text more
    78. 

  78.           explicative</p></li></ul></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch02s08.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch02.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch03.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2.0 Release candidate 2 </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 3. System Requirements</td></tr></table></div></body></html>
    79. 

  79.