Re: XML-RPC implementation for a channel server

From: Date: Mon, 12 Apr 2004 23:01:11 +0000
Subject: Re: XML-RPC implementation for a channel server
References: 1  Groups: php.pear.core 
Request: Send a blank email to pear-core+get-268@lists.php.net to get a copy of this message
Hi Greg, I get the idea, but I don't quite get how you wanted to represent this? In the array below, does the key ("pear-install") represent the function/command name? Is the URL the XML-RPC server URL, or something abstract like a namespace URL? I would like to see this part of the infrastructure simplified, instead of adding more bloat/complexity (which I consider SOAP to be :-). I have some code locally that implements "PHP-RPC" as an alternative, which essentially does the same as XML-RPC but uses serialize() and unserialize() to pass around values. - Stig On Mon, 2004-04-12 at 08:36, Greg Beaver wrote: > Hi all, > > I'd like to propose that the best way to implement channels server-side > is to require a new xml-rpc introspection function called > pear.getCapabilities to match the system.getCapabilities function. > Using this method, we can allow people to implement a required subset of > xml-rpc functions by documenting the minimum functions needed to perform > a function. For instance, the minimum functions needed to install a > package are package.listLatestReleases, and package.info. These > functions could be described as pear-install version 1.0, so a server > could return > > pear-install => array('url' => > 'http://pear.php.net/pearweb/pear-install.php', > 'version' => 1) > > if they implement this particular protocol. In the future, when a > change is made, the version can be used by the installer to determine > what download methods/signatures are available without the need to query > each function individually, and to gracefully exit if the API is too old. > > Another advantage is that test suites can be provided to allow channel > providers to verify that their xml-rpc works as it should, and can be > required to allow pear.php.net to verify the capabilities. This way, > when a new server is added, the capabilities can be documented right off > the bat, or servers that don't provide a proper xml-rpc interface can be > dropped automatically. > > Unfortunately, system.getCapabilities appears to be internal to the > server and read-only. system.methodSignature does not return any > versioning information, making it useless for determining the meaning of > its return. > > Ultimately, we will want to move to SOAP since it is the standard > replacement for XML-RPC, but this is post PEAR2. > > Regards, > Greg

« previous php.pear.core (#268) next »