Re: RFC: REST-RPC

>The piece of the picture that's still lacking standardization (and I think  
>this is weird) is the API applications use to make RPC calls.

I don't quite see an opportunity for standardization there.  A library
for XML-RPC or a similar protocol is little more than a translator
between the protocol and some API.  If there are two libraries, it's
probably because some people like the API one provides more than the
API the other provides.  Why would you have two different
implementations of a single standard API?  Also, these RPC protocols
have another reason to have varying APIs: People want to make remote
procedure calls in a way very similar to making a local procedure
call, so the API is tailored to each individual programming language.

In the database example, I note that a database manager does a whole
lot more than translate an API to another language, so there's lots of
reason to swap Mysql for ODBC without changing application code.  But
why would you swap one PHP XML-RPC client library for another unless
you wanted to change application code?


Incidentally, on the subject of REST-RPC: there apparently are no
libraries for it.  What I read calls that a feature: you can use
standard services to do things such as parse XML and make HTTP
requests, and don't need a special REST-RPC library.  I think the same
is true of XML-RPC, though.  You don't have to use any of the various
libraries that exist.  You can just duplicate what they do (they use
standard XML and HTTP services) in your own program.

-- 
Bryan Henderson                                    Phone 408-621-2000
San Jose, California


 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/xml-rpc/

<*> To unsubscribe from this group, send an email to:
    xml-rpc-unsubscribe@xxxxxxxxxxxxxxx

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/