XML-RPC造句

In particular, I looked at RPC, XML-RPC, and SOAP, dissecting what is included with each technology.

You can turn on debugging in the XML-RPC object to verify this.

You can easy change the technology (for example from XML-RPC to RMI).

You may have also learned that your business needs could be met by using a simpler package than SOAP, like one of the XML-RPC libraries found at the Userland XML-RPC site (see Resources).

Consider, for example, the fact that your XML data can be sent, relatively unchanged, into an XML-RPC call with little to no overhead.

Also, imagine the XML transformations (XSLT) that occur allowing XML-RPC systems with disparate formats to convert from one to the other easily.

XML-RPC has a few additional artifacts -- like the need to wrap the whole object in a one-item tuple -- but these are minor issues.

也许您还了解到可以用更简单的包而不是SOAP 来满足商业需求，如在Userland XML-RPC站点（请参阅参考资料）上找到的 XML-RPC库之一。

First, what it's not: This isn't a XML-RPC-style web service, document-style web service, SOAP web service, or Representational State Transfer (REST) (noun-based) request web service.

XML-RPC有几个额外的构件 ―就象需要将整个对象封装在包含一项的元组中 ―但这些都是小问题。

并且使用SOAP（与XML-RPC单独对比），可以用SOAP的故障机制，API的标准部分，来转播客户机可能发生问题的大量信息。

首先我们限定它不是什么：它不是一个 XML-RPC样式的Webservices 、文件样式的Web services 、SOAPWeb services或代表*状态传输（Representational State Transfer，REST）（基于名词）请求Web services 。