Re: [PEPr] Comment on XML::XML_RPC2

Sergio Carvalho wrote:

Davey Shafik wrote:

Davey Shafik (http://pear.php.net/user/davey) has commented on the proposal for XML::XML_RPC2. Comment: I'd like to see more examples, and I don't understand what method the client example is calling. Is it calling the "test" method with "PEAR_Server" as the argument, or is "PEAR_Server" the method and "test" lord knows what? Also, I'd like to see examples of docblocked classes which have methods with arguments, and a breakdown of what is used to expose it.

Here: http://www.sergiocarvalho.com/wiki/XmlRpc2Examples/ Tell me if the page doesn't clear all doubts.

I'd like it possible if we could collaborate on some sort of API to make it possible to expose the same code automatically as SOAP (through Crtx_SOAP) or XML-RPC, thoughts?

I think this is an excellent idea. We can start a wiki page to sketch a common interface for RPC packages. I'd like it to be as simple as possible, and to work with at least XML-RPC, SOAP and REST.

I don't know REST, will look into it ;)

Finally, the version should be 0.x.x, 2.0.0 will be the first stable release :)

I have some doubts. There's already an XML_RPC package, version 1.x.x. XML_RPC can't go backwards, and XML_RPC2 is so named just to allow coexistence of installed versions 1 and 2. The package is really XML_RPC. So, this should be 2.0.0-alpha. When it goes API-stable, it becomes 2.0.0-beta and then 2.0.0 when bug-stable.

I know it sounds wonky, but in PEAR any package that is not stable, may not have an x.0.0 version, unless its an RC of a stable release. What this means is, that we have the package XML_RPC2, who's sub-RC version of 0.x.x. Put another way, we always signify non-stable packages as 0.x.x no matter what major version of said package they will become.

Would you like a third developer? :)

All hands to battle-stations :-) Any help is appreciated. Cheers, Sérgio