Re: Re: XML_RPC_Easy (pre)proposal

Philippe Jausions wrote:

Justin Patrin wrote:

On 9/26/05, Lukas Smith <lsmith@php.net> wrote:

Sergio Carvalho wrote:

As far as I'm concerned, I'm not producing any more efforts to get the package in. One full year is long enough. The code remains LGPL, so anyone is free to pick it up and climb the long ladder to PEAR acceptance. I plan to take some time and develop xml-rpc for Services_webservice.

Totaly understandable. I am quite dissapointed with all parties involved.

I personally think that the Group should force this through now. If Dan didn't have time for a whole year to check this out (a year is really far too long to wait) then unfortunately we can't wait for him any longer.

As a co-maintainer of Services_Webservice we could really re-use some of Sergio's great work on XML_RPC2 (Sergio contact me offlist on how we would handle "merging" your code.) We currently have in mind to expand the implementation of the package from SOAP/ext to other protocols, including XMLRPC. With some refactoring, we could use the code to allow the same web service class to handle SOAP, XMLRPC, JSON, ReST, etc... However, Services_Webservice is only server-side, so the client-side of XML_RPC2 would still be useful as a standalone package. This is only an FYI on what we're trying to accomplish to somewhat circumvent the problem and get things going. -Philippe

Philippe, I also have looked at this, see http://svn.crtx.org/browse.php/Crtx_WebServices/ for proof ;) I had planned to make it possible to automatically expose any code as SOAP/XML-RPC/REST, however REST doesn't really lend to that (because its technically arbitrary). So I wanted to do it for just SOAP/XML-RPC. Though it wouldn't be the only way to create web services, there should be some sort of manual way in which it can be done, so that say, REST can use it. If you would perhaps like to put our heads together, that would be cool :) - Davey