XML-RPC造句怎麼寫

也許您還了解到可以用更簡單的包而不是SOAP 來滿足商業需求，如在Userland XML-RPC站點（請參閱參考資料）上找到的 XML-RPC庫之一。

XML-RPC有幾個額外的構件 ―就象需要將整個物件封裝在包含一項的元組中 ―但這些都是小問題。

首先我們限定它不是什麼：它不是一個 XML-RPC樣式的Webservices 、檔案樣式的Web services 、SOAPWeb services或代表*狀態傳輸（Representational State Transfer，REST）（基於名詞）請求Web services 。

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

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).

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

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.

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

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

並且使用SOAP（與XML-RPC單獨對比），可以用SOAP的故障機制，API的標準部分，來轉播客戶機可能發生問題的大量資訊。

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.

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