Remote Procedure Calls: Difference between revisions
No edit summary |
No edit summary |
||
| Line 8: | Line 8: | ||
Google also offers an extensive suite of <a href="http://eutils.ncbi.nlm.nih.gov/entrez/query/static/eutils_help.html">APIs</A>. | Google also offers an extensive suite of <a href="http://eutils.ncbi.nlm.nih.gov/entrez/query/static/eutils_help.html">APIs</A>. | ||
[[Category:XML]] | |||
[[Category:RPC]] | |||
[[Category:XMLRPC]] | |||
Revision as of 21:05, 20 September 2007
"Remote Procedure Calls" (RPC) means different things to different people. Here, combined with XML, it refers to methods of driving services on one computer from another. We use the Python XML RPC libraries to support both Perl and Python clients. We offer a range of services at services.compbio.ucsf.edu. it is our goal to support RPC calls for every service available on our websites, although that still seems a long way off.
RPC calls have not caught on as well as one might have expected, somewhat due to the lack of standards in the field.
Entrez, including PubChem and PubMed, offer <a href="http://eutils.ncbi.nlm.nih.gov/entrez/query/static/eutils_help.html">E-utils</A>.
Google also offers an extensive suite of <a href="http://eutils.ncbi.nlm.nih.gov/entrez/query/static/eutils_help.html">APIs</A>.