In this article we have dealt with the most basic and important routines that any RPC client and server application makes.
在本文中，我们讨论了任何RPC客户机和服务器应用程序调用的最基本、最重要的例程。
During the server RPC application initialization, it registers the interface with RPC runtime library.
服务器RPC应用程序初始化期间它会向RPC运行时库注册接口。
The local endpoint map database is used to store all the endpoints of RPC server processes running on that host.
本地端点映射数据库用于存储在此主机上运行的RPC服务器进程的所有端点。
To further simplify the deployment of their applications RPC has structured both the client and server to be included as the same installation.
为了进一步简化应用的部署，RPC应用已经将客户端和服务器端打包在同一个安装包中。
DCE provides a secure communication channel between a client and a server through an authenticated RPC mechanism.
DCE通过一个认证RPC机制在客户机和服务器之间提供了一个安全的通信通道。
This section gives an overview of registering an interface specification with the RPC runtime in the server application and unregistering it.
本节概述在服务器应用程序中向RPC运行时注册接口规范和取消注册的例程。
Encoding other types requires modifying the actual RPC server and client themselves.
编码其它类型需要修改实际的RPC服务器和客户机自身。
Normally, a RPC server application advertises or exports its location, that is the binding information which gets stored in a name service database.
通常，RPC服务器应用程序会公布或导出它的位置，位置信息以绑定信息的形式存储在名称服务数据库中。
Figure1 illustrates the way a client and server completes an RPC call over the network.
图1说明客户机和服务器通过网络完成RPC调用的方式。
Thus, every cache miss on the server triggered a callback RPC that had to fetch the user's credential (STKT + PAC) in its entirety.
因此，服务器上的每次缓存缺页都会触发一个RPC回调，它会获取整个完整的用户证书(STKT +PAC)。
The RPC server bundles up the results of the procedure and sends those results back to the caller.
RPC服务器将过程的结果打包并将那些结果发送回调用者。
The responsibility to initiate an authenticated RPC to the target server (through an appropriate DCE API call) lies with the client applications.
（通过一个适当的DCEAPI调用）向目标服务器发起一个已认证的RPC的职责在于客户机程序。
Finally the server then goes ahead and executes the RPC call and returns the results back to the client.
最后，服务器执行RPC调用，将结果返回到客户端。
Client now makes an RPC call to the target server sending it the PSTkt containing session key and the PAC.
客户端现在向目标服务器发出一个RPC调用，向它发送包含会话密钥和PAC的PSTkt。
Another parameter you can tune is timeo, which specifies the time out value for the RPC calls to the server.
还有一个参数您可以进行优化，即timeo，该参数指定了对服务器的RPC调用的超时值。
The client and server stubs communicate using the RPC runtime library.
客户机和服务器stub使用RPC运行时库通信。
What follows is an example process flow of a client synchronizing orders with a server using RPC calls over Web services.
下面是一个示例处理流程，使用RPCWeb服务来同步客户机和服务器上的订单。
Then on the server side of the RPC handler, you need to access this SOAP message to extract the SOAP headers to identify the partner's IDs.
然后，您需要在RPC处理程序的服务器端访问此SOAP消息，以提取SOAPHeader来标识合作伙伴的ID。
On the server side, the listener for SOAP RPC messages is implemented as a servlet.
在服务器端，SOAPRPC消息的侦听器被作为servlet实现。
After establishing the port number for the mount (via the get_port request RPC call to the remote server), the client performs an RPC mount request.
确认了加载端口号之后（通过 get_port请求对远程服务器RPC调用），客户端执行 RPCmount 请求。
Before we go into the details of each of these services, you should keep in mind that all these services are implemented by a single RPC server, called a security daemon or secd.
在了解每个服务的详细信息之前，您应该记住，所有这些服务都是由一个RPC服务器实现的，该服务器称为安全后台程序或secd。
The server RPC runtime library receives this incoming RPC call, passes it to the server stub which converts it to the format that server understands for execution.
服务器RPC运行时库接收到达的RPC调用，把它传递给服务器stub，服务器stub把它转换为服务器可以理解的格式。
The client makes an RPC call to the server, and the STkt containing the session key passed as a part of the RPC protocol.
客户端向服务器发出RPC调用，并将包含会话密钥的STkt作为RPC协议的一部分传递给服务器。
This is all done on the server side through a special servlet called the RPC router, which is part of the Application server runtime.
所有这些都是在服务器端通过一个名为rpc路由器的特殊servlet完成的，该servlet是ApplicationServer运行时的一部分。
Those unfamiliar should rest assured that RPC support allows very tight coupling with server-side logic in an intuitive manner.
那些不熟悉RPC 的用户也可以放心，OpenLaszlo 中的 RPC支持允许以一种直观的方式与服务器端逻辑紧密耦合。
Even though you can write your own JAX-RPC handlers, the application server vendor can decide, based on configuration and security policies, whether to allow a new handler or not.
尽管您能编写自己的JAX - RPC处理程序，应用程序服务器提供商也能够根据配置和安全策略决定是否允许一个新的处理程序存在。
In both DCOM and CORBA, the interactions between a client process and an object server are implemented as object-oriented RPC-style communications.
在DCOM和CORBA中，客户进程与对象服务器之间的互相作用是作为面向对象的rpc式通信来实现的。
We will use JAX-RPC compliant engine as the platform of choice for the service implementation (server-side).
我们将使用符合JAX - RPC要求的引擎作为供选择的服务实现平台(服务器端)。
The subsequent block of code initializes the XML-RPC client connection to the blog server.
接下来的代码初始化到博客服务器的XML - RPC客户端连接。
On the server side, you can also use a JAX-RPC handler to deal with implicit headers.
在服务器端，还可以使用JAX - RPC处理程序处理隐式消息头。
应用推荐