Re: [PEPr] -1 for XML::XML_RPC2
| From: | Davey | Date: | Fri, 13 May 2005 01:26:23 +0000 |
| Subject: | Re: [PEPr] -1 for XML::XML_RPC2 | ||
| References: | 1 2 3 | Groups: | php.pear.dev php.pear.dev |
| Request: | Send a blank email to pear-dev+get-37615@lists.php.net to get a copy of this message | ||
Sergio Carvalho wrote:
Davey Shafik wrote:Sergio, ext/soap uses this API: $soapClient->remoteMethod($args) You can't get more simple. In addition there is a __soapCall() method. This is because not all languages have the same restrictions on method naming as PHP does and therefore you can't do $soapClient->someWeirdMethodName() and don't want to use { }. And to create the server, you simply tell it the class name (or pass it an object, I don't remember off the top of my head) - DaveyDavey Shafik (http://pear.php.net/user/davey) 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=davey Comment: I don't see this as being much of an improvement. I want to see something as simple as ext/soap. It should be as close to identical API wise as ext/soap and require no more or less work. - DaveyWhy would you want to call methods using $proxy->soapCall('methodName', ...) when you can use $proxy->methodName(... . Or why would you want to setup a server doing $server->addFunction ad nauseam when you can just point the server to an interface class? I'd more accept see a wrapper PEAR class over ext/soap which adds catchall use, docblock parsing and Exceptions. -- Sérgio