Table 1: XML-RPC API for account info.
表1:账号信息的XML - RPCapi。
Lastly, let's look at the XML-RPC protocol.
最后,让我们考察一下XML - RPC协议。
This integer is then returned to the XML-RPC client.
然后这个整数返回给XML-RPC 客户端。
An introductory XML-RPC program needs a meatier framework.
XML - RPC的入门程序需要一个更丰富的框架。
Apache XML-RPC: Download the latest version for your system.
Apache XML - RPC:下载适合您系统的最新版本。
You can turn on debugging in the XML-RPC object to verify this.
您可以在XML - RPC对象中开启调试来校验它。
XML-RPC defines procedure calls encoded in XML and communicated over HTTP.
XML - RPC定义了使用XML编码并通过HTTP通信的过程调用。
In RPC (and XML-RPC), encoding can only occur for a predefined set of data types.
在RPC(和XML - RPC)中,编码只可能针对预先定义的数据类型发生。
Again, the success or failure of this operation is returned to the XML-RPC client.
此外,这个操作的成功或失败都返回给XML - RPC客户端。
The front-end code can only get to the underlying data by making these XML-RPC calls.
前端代码只有通过调用这些XML - RPC才能够接触到底层数据。
Many people have commented to us that XML-RPC can fill most of the roles that SOAP does.
许多人已经向我们说过XML - RPC可以胜任SOAP能胜任的大多数角色。
Table 1 shows the XML-RPC middleware API for this application's user accounts data store.
表1给出了这个应用程序的用户账号数据存储的XML - RPC中间件api。
The subsequent block of code initializes the XML-RPC client connection to the blog server.
接下来的代码初始化到博客服务器的XML - RPC客户端连接。
Suppose you're writing a PHP script that receives XML-RPC requests and generates responses.
假定正在编写php脚本,用来接收XML - RPC请求并生成响应。
I've also added a fault method that sends an XML-RPC fault response when something goes wrong.
我还添加了fault方法,当发生故障时将发送XML - RPC错误响应。
There is no requirement in the Perl XML-RPC library that there be a Perl function called sum().
在PerlXML-RPC库中不需要有一个称为sum() 的 Perl函数。
Given this brief theoretical background, let's solve a real world problem with XML-RPC middleware.
根据这个简短的理论背景,让我们使用XML - RPC中间件来解决现实世界中的一个问题。
These developers could gain a lot from moving to a SOAP-based or XML-RPC-based communication model.
这些开发人员可以从转向基于SOAP或基于XML - RPC的通信模型中获益匪浅。
In particular, I looked at RPC, XML-RPC, and SOAP, dissecting what is included with each technology.
特别是,我查看了RPC、XML - RPC和SOAP,剖析了每项技术所包含的。
I've compared SOAP to RPC, XML-RPC, and RMI, examining the differences among them and the pros and cons.
我已经将soap与rpc、XML - RPC和RMI作了比较,研究了它们之间的不同以及优点和缺点。
Finally, picture an XML-RPC sender at one place of business sending an XML-RPC payload to another business.
最后,想象在某处企业的XML - RPC发送方将一个XML - RPC有效负载发送到另一个企业。
Using XML for messaging has become popular enough to have produced these two alternatives: XML-RPC and SOAP.
使用XML进行消息传递已经非常流行,以至于已经产生了两个替代品:XML - RPC和SOAP。
Also like the Perl library, PHP allows the programmer to look at the underlying XML-RPC conversation for debugging.
同样与perl库类似,php使程序员能够查看底层的XML - RPC会话,以便用于调试。
The note on SOAP submitted to the W3C defines two major items that SOAP contains in addition to its basic XML-RPC features.
提交给W3C的有关SOAP的说明定义了除了基本的XML - RPC特性之外SOAP所包含的两项主要项。
XML-RPC: Study the XML-RPC specification and its variety of implementations for RPC in a distributed computing environment.
XML - RPC:学习XML - RPC规范以及分布式计算环境中的RPC的各种实现。
The four technologies that you will examine in this column are SOAP, CORBA, XML-RPC, and good, old-fashioned low-level sockets.
在本专栏中,您将要探讨的四项技术是SOAP、CORBA、XML - RPC和优秀的、传统的、低级别的套接字。
Until fairly recently, XML-RPC limited strings to only ASCII, thereby losing one of the great benefits of XML in the first place.
直到最近,XML - RPC还将字符串限制为ascii,因而首先就放弃了XML的主要优点之一。
XML-RPC is designed to be as simple as possible, while allowing complex data structures to be transmitted, processed and returned.
XML - RPC的设计力求简单,并同时允许传输、处理和返回复杂数据结构。
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.
XML-RPC有几个额外的构件 ―就象需要将整个对象封装在包含一项的元组中 ―但这些都是小问题。
You may have been surprised to discover that many of SOAP's "features" actually are XML-RPC features that are not intrinsic to SOAP.
您也许奇怪地发现许多SOAP的“特性”,实际上是XML-RPC的特性,不是 SOAP固有的。
应用推荐