Re: [PEPr] +1 for XML::XML_RPC2
| From: | Greg Beaver | Date: | Thu, 12 May 2005 03:22:09 +0000 |
| Subject: | Re: [PEPr] +1 for XML::XML_RPC2 | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-37578@lists.php.net to get a copy of this message | ||
Sergio Carvalho wrote:
Joshua Eichorn wrote:Josh is not saying he wants you to write a backend for xmlrpci, but to re-design the API as close to xmlrpci as possible (this is also part of my complaint). xmlrpci is designed to be as similar to ext/soap as possible, you can reference those docs. Correct me if I'm wrong Josh. The old xmlrpc extension is unmaintained and does not fully work in PHP 5 (check php-internals archives/pecl-dev archives). For an example, try making it parse any invalid xml returned from the server, and you'll get an infinite loop or segfault. GregJoshua Eichorn (http://pear.php.net/user/jeichorn) has voted +1 on the proposal for XML::XML_RPC2. Proposal information: http://pear.php.net/pepr/pepr-proposal-show.php?id=172 Vote information: http://pear.php.net/pepr/pepr-vote-show.php?id=172&handle=jeichorn This vote is conditional. The condition is: I'm concerned that your punting the integration work with the xmlrpc extension. Especially since there is work happening on xmlrpci which provides and OO api to xmlrpc. Can you at least do a review of the extension apis to see how integrating them will affect your design, and also note the differences in your api from xmlrpci.The package design was thought out to use the 'old' xmlrpc extension. xmplrci follows the xmlrpc extension close enough that integration shouldn't be a problem. xmlprci, however, is still poorly documented -- the only docs I've found are the code itself.