Re: XML-RPC implementation for a channel server
| From: | Jan Schneider | Date: | Tue, 13 Apr 2004 09:08:51 +0000 |
| Subject: | Re: XML-RPC implementation for a channel server | ||
| References: | 1 2 3 | Groups: | php.pear.core |
| Request: | Send a blank email to pear-core+get-270@lists.php.net to get a copy of this message | ||
Zitat von Greg Beaver <greg@chiaraquartet.net>:
the key is an abstract representation for the xml-rpc functions that would be necessary to install a package (i.e., package.listLatestReleases, package.info, versions 1.0). other keys might be the commands needed to implement the remote-list or search commands.I don't think that you really need fine-grained versioning on method names, once you have a well layouted api. If you really ever need a different method implementation/signature that is incompatible to the current version, you can always number the method names, like with the getopt() methods in Console_Getopt or the PEAR package names with new major versions.
I like PHP-RPC except for the inability to interoperate with servers written in other languages (which may happen someday).100% agreed. You should stick with a standard, even if there is a lighter alternative. XML-RPC is already a very lightweight protocol. Jan. -- http://www.horde.org - The Horde Project http://www.ammma.de - Neue Wege des Lernens http://www.tip4all.de - Deine private Tippgemeinschaft