In this article we have dealt with the most basic and important routines that any RPC client and server application makes.
在本文中，我们讨论了任何RPC客户机和服务器应用程序调用的最基本、最重要的例程。
DCE provides a secure communication channel between a client and a server through an authenticated RPC mechanism.
DCE通过一个认证RPC机制在客户机和服务器之间提供了一个安全的通信通道。
Encoding other types requires modifying the actual RPC server and client themselves.
编码其它类型需要修改实际的RPC服务器和客户机自身。
Figure1 illustrates the way a client and server completes an RPC call over the network.
图1说明客户机和服务器通过网络完成RPC调用的方式。
The invocations from client to RPC adapter are all based on JSON RPC, and the returned data is encapsulated in JSON objects, which can be parsed on the client side very quickly.
由客户机发出的对RPC适配器的调用全部基于JSON RPC，因此返回的数据被封装到 JSON对象中，后者可以在客户端快速解析。
The client-site classes for the RPC proxy are also located in this package.
RPC代理的客户端类也在这个包中。
The client application receives the result from client stub and finishes the RPC call.
客户机应用程序从客户机stub接收结果并完成RPC调用。
The client RPC runtime receives it, gives it to client stub which passes the execution result to the client process.
客户机rpc运行时接收执行结果，传递给客户机stub，客户机stub再把它传递给客户机进程。
The client object files along with the client stub file is linked with the RPC runtime library to generate the client executable.
客户机对象文件和客户机stub文件与RPC运行时库链接，生成客户机可执行程序。
With a few lines of code similar to that shown below, they were able to render HTML based reports from the server directly in the Eclipse RPC based client.
只需一些类似于下面的代码，就能在基于EclipseRPC的客户端上直接获得基于HTML的报表，而这些报表都来自于服务器端。
In this approach, you have to configure the RPC handler in the client stub so that you can modify the MessageContext object to contain the partner's IDs in the handler.
在此方法中，您必须在客户机存根中配置RPC处理程序，以便对MessageContext对象进行修改，使得在该处理程序中包含合作伙伴的ID。
The client and server stubs communicate using the RPC runtime library.
客户机和服务器stub使用RPC运行时库通信。
Next, the client issues a LOOKUP RPC request to see if the requested file exists.
接下来，客户端发出LOOKUPRPC请求来查看所请求的文件是否存在。
To further simplify the deployment of their applications RPC has structured both the client and server to be included as the same installation.
为了进一步简化应用的部署，RPC应用已经将客户端和服务器端打包在同一个安装包中。
Note that the definition of JAX-RPC client is relative to the service which the client communicates with, and stubs for different services are deemed as different clients.
请注意JAX - RPC客户端的定义是相对于服务的，这些服务与客户端进行通信，并且不同服务的存根被认为是不同的客户端。
The results from the method are marshaled back to the client using the same JAX-RPC and SAAJ interfaces.
从这个方法返回的结果使用相同的JAX-RPC和SAAJ 接口被数据编入回到客户机。
With the file identified in the remote file system, the client can issue READ RPC requests.
利用在远程文件系统中指定的文件，客户端能够触发READ RPC请求。
If the number of lines of code for the SQL, XML-RPC listener, and client are counted, this middleware system was weighs in under 600 lines of code.
如果把SQL、XML-RPC监听器和客户端的代码行数都计算在内，估计这个中间件系统的代码会低于 600 行。
For the client, I will deploy the handler using the JAX-RPC programmatic interface.
对于客户端，我将使用JAX - RPC程序化接口来部署处理程序。
The subsequent block of code initializes the XML-RPC client connection to the blog server.
接下来的代码初始化到博客服务器的XML - RPC客户端连接。
One of the beauties of JAX-RPC for the client is its ability to associate context information with an endpoint's remote method call.
客户机JAX - RPC的亮点之一就在于它能把上下文信息和端点的远程方法调用关联起来。
Again, the success or failure of this operation is returned to the XML-RPC client.
此外，这个操作的成功或失败都返回给XML - RPC客户端。
There's no OPEN procedure within RPC; instead, the client simply checks to see if the directory and file exist within the mounted file system.
在RPC内没有OPEN程序；反之，客户端仅检查目录和文件是否存在于所加载的文件系统中。
This is mainly used for RPC based client-server invocation.
这主要用于基于RPC 的客户机／服务器调用。
To help debug errors, I used the JSON-RPC stand-alone client lib, as shown in Listing 20.
为了帮助调试错误，我使用单独的JSON - RPC客户机库，见清单20。
In the meantime, the client is also required to toggle a special flag to notify the JAX-RPC runtime system to maintain the client sessions.
同时，客户端也需要切换一个特定的标志来通知JAX - RPC运行时系统对客户端会话进行维护。
This integer is then returned to the XML-RPC client.
然后这个整数返回给XML-RPC 客户端。
Remote procedure call (RPC) is a technique for constructing distributed, client-server-based applications.
远程过程调用(rpc)是一种用于构造分布式的、基于客户端-服务器的应用程序的技术。
Background for the two questions: I have succeeded in accessing the overloaded operations of a standard Web service using the JAX-RPC client through SOAP binding.
这两个问题的背景是：我已经通过SOAP绑定使用JAX - RPC客户机成功地访问了标准Web服务的过载操作。
Unlike a typical Web browser which handles sessions automatically, the JAX-RPC client does not participate in a session with the target service endpoint by default.
与自动处理会话的典型Web浏览器不同的是，JAX - RPC客户端并不缺省的使用目标服务端点参与会话。
应用推荐