<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Fri, 08 Aug 2008 16:20:24 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Evert Pot's Blog: PHPRPC and PHP frameworks]]></title>
      <guid>http://www.phpdeveloper.org/news/8442</guid>
      <link>http://www.phpdeveloper.org/news/8442</link>
      <description><![CDATA[<p>
In an effort to spread PHP-RPC functionality around as much as possible, <i>Evert Pot</i> has <a href="http://www.rooftopsolutions.nl/article/145">suggested his code</a> to three of the major sources for application development - the <a href="http://pear.php.net">PEAR project</a>, the <a href="http://www.solarphp.com">Solar Framework</a> and the <a href="http://framework.zend.com">Zend Framework</a>.
</p>
<blockquote>
I started the process to submit PHPRPC to the major frameworks. I feel like I should submit it to all the major frameworks, so I can make sure people can use PHP-RPC regardless of their framework of choice.
</blockquote>
<p>
In PEAR, it has been submitted as <a href="http://wiki.pear.php.net/index.php/PEAR2_Standards">a PEAR2 package</a>, in the Solar Framework as an open ticket (so far) and in the Zend Framework as just an idea (no formal or informal kind of submission yet).
</p>]]></description>
      <pubDate>Mon, 13 Aug 2007 16:27:00 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Evert Pot's Blog: PHP-RPC update 4]]></title>
      <guid>http://www.phpdeveloper.org/news/8405</guid>
      <link>http://www.phpdeveloper.org/news/8405</link>
      <description><![CDATA[<p>
<i>Evert Pot</i> has <a href="http://www.rooftopsolutions.nl/article/144">posted his latest update</a> for the PHP-RPC spec for PHP - PHP-RPC update 4 - hopefully the last:
</p>
<blockquote>
<p>
Unless somebody has some great feedback with stuff I overlooked - it might need some clarification and better writing here and there, but I think the general idea is there.
</p>
<p>
The api for the server class currently works the exact same as before, but support for multi-calls has been added. I also added a client class, which is helpful when you surpass the prototyping phase and you need a more decent way to interact with the service.
</p>
</blockquote>
<p>
<a href="http://www.rooftopsolutions.nl/article/144">Details on the proposal</a> are in the post including code for an example usage (and a multi-call use) and the official version of the latest proposal, version 0.4. This is broken out into the two sides of the proposed method - the request and the server - and how they would handle the interaction.
</p>]]></description>
      <pubDate>Tue, 07 Aug 2007 11:09:00 -0500</pubDate>
    </item>
  </channel>
</rss>
