The sending server makes a remote invocation.
发送服务器进行远程调用。
The JSR 172 remote invocation API consists of the following packages.
JSR 172远程调用API包括下面这些包。
The Outbound request makes the remote invocation to the target server.
Outbound请求对目标服务器进行远程调用。
Note how the remote invocation was performed in its own thread of execution.
注意远程调用是如何在自己的执行线程中执行的。
The Inbound request component receives the remote invocation on the target server side.
Inbound请求组件在目标服务器端接收远程调用。
By encouraging remote invocation we can decouple location, platform, and programming language.
通过鼓励进行远程调用，我们可以进行位置、平台和编程语言分离。
Network latency: With remote invocation of the rule services comes the issue of network latency.
网络延迟：对规则服务的远程调用伴随而来的是网络延迟问题。
Like many other remote invocation frameworks (such as RMI, EJB, and JAX-RPC), JMX is interface-based.
像其他许多远程调用框架(RMI、EJB和JAX - RPC)一样，JMX也是基于接口的。
Collected from the protocol used for making the remote invocation (in this case, CSIv2) over the network.
从用于通过网络进行远程调用的协议(在这个示例中是CSIv2)中收集到的信息。
The sending server makes a remote invocation and places the identity for the invoker into the request.
发送服务器进行远程调用，并将调用者的标识放到请求中。
First of all, the lifetime of tokens are not restricted to a single remote invocation, or to a single protocol.
首先，令牌的生存期并不局限于单个远程调用、或单个协议。
Read a remote invocation from the request, execute it, and write the remote invocation result to the response.
从请求中读取远程调用，执行调用，然后将调用结果写到响应中去。
The Login module returns the subject to the Outbound request so the request can use it for making the remote invocation.
Login模块向Outbound请求返回主题，所以请求可以使用它进行远程调用。
Before making the remote invocation, the application code has to create a new subject that is valid on the target server.
在进行远程调用之前，应用程序代码必须创建一个在目标服务器上有效的新主题。
I design the scheme to loosen the remote invocation coupling from four aspects, and show how to achieve these coupling.
设计了从四个方面来降低远程调用系统耦合度的方案，并给出了实现方法。
The RMI framework then manages communication with the remote object, which results in remote invocation of the required methods.
然后 RMI框架管理与远程对象的通信，形成对所需方法的远程调用。
In this particular sample, the asserted identity for the server side is simply sent as a method parameter of the remote invocation.
在这个特定的示例中，服务器端的断言标识作为远程调用的方法参数发送。
The outbound request component USES the login module to perform a login to make the remote invocation with the appropriate identity.
出站请求组件使用Login模块以执行登录，以使用合适的标识进行远程调用。
Should a service designer be permitted free choice between local and remote invocation, between synchronous and asynchronous invocation?
服务设计人员是否可以自由选择本地调用和远程调用、同步调用和异步调用？
Before the sending server makes the remote invocation, the client code performs a login using a custom application login configuration.
在发送服务器进行远程调用之前，客户机代码使用自定义的应用程序登录配置进行登录。
However, because Web services are more practical in a remote invocation environment, this set-up is not very practical in a real-world environment.
然而，由于Web服务在远程调用环境中更实用，因此，该客户端安装在实际环境中并不是很实用。
This simplicity is possible due to the JSR 172 stub and runtime, which, as previously mentioned, hide most of the details related to remote invocation.
由于有JSR 172存根和运行时，实现这种简单的应用程序是可能的，正如前面提到的，JSR 172 存根和运行时把与远程调用相关的大部分细节都隐藏了。
However, most of the current rule engines are lack of remote invocation interfaces, so they can't be integrated effectively in the distributed conditions.
然而，当前大多数规则引擎缺少远程调用的接口，在分布式应用方面存在着缺陷，无法被有效地集成。
This is because remote invocations in JSR 172 are blocking calls, and if invoked in the main event thread, the user interface will freeze until the remote invocation completes.
由于JSR 172中的远程调用是按模块进行的，而且如果在主事件线程中调用，用户界面会冻结，直到远程调用结束。
From there, I'll go on to compare SOAP, and RPC in general, with one of its biggest competitors, remote method invocation (RMI).
从那里，我继续将SOAP和一般而言的RPC与它的最大竞争对手之一，远程方法调用(rmi)相比较。
However, EJB will still have a place in defining endpoints for message delivery, remote and asynchronous method invocation, timers, etc.
然而EJB在为消息传输定义端点、远程与异步方法调用、定时器等领域还是有一席之地的。
Intraprocess communication avoids all the overhead of a remote service invocation, including serialization, encryption, traversing the network stack, and network latency.
进程内通信可以避免远程服务调用的所有开销，包括序列化、加密、遍历网络堆栈和网络延迟。
The "bridge" role from the broker pattern was then implemented using the template method pattern to support remote service invocation using several different underlying communication technologies.
中介模式的“桥接”角色是使用模板方法模式实现的，它通过几种不同的基础通信技术，为远程服务调用提供支持。
A dispatching approach refers to where remote callers send their invocation messages and how the method invocations are routed to the method implementation object.
调度方法将引用远程调用程序发送调用消息的位置，以及如何将方法调用路由到方法实现对象中。
You can then map the events to remote object invocation, leaving the details of the code out of your views and model.
然后将这些事件映射到远程对象调用，以便将代码细节置于视图和模型之外。
应用推荐