Network latency: With remote invocation of the rule services comes the issue of network latency.
网络延迟：对规则服务的远程调用伴随而来的是网络延迟问题。
The real invocation of the rule engine is delegated to a simple rule session.
规则引擎的真正调用会被分配到一个简单的规则会话中。
Following the same rule given in the one-way invocation example, the local-time picture is shown in Figure 16.
遵循单向调用示例中给出的相同规则，图16显示了本地时间图形。
Figure 14 shows the model of the rule set invocation using SCA POJO component.
图14显示使用SCAPOJO组件调用规则集的模型。
The Rule Execution Server includes components for synchronous, asynchronous, and Web service-based invocation of business rules, as well as a Web administration console.
RuleExecutionServer包含对业务规则进行同步、异步和基于Web服务的调用的组件，还包含一个 Web管理控制台。
Rule services deployed in ILOG JRules can be accessed via EJB invocation, locally or remotely.
可以通过EJB调用本地或远程地访问ILOGJRules中部署的规则服务。
The only exception to this rule is when a mediation flow component is called using the invokeAsyncWithCallback invocation style.
此规则唯一的例外是使用invokeAsyncWithCallback 调用样式调用中介流组件时。
ILOG JRules rule execution Server: a J2SE - and J2EE-compliant rule execution environment that includes components for synchronous, asynchronous, and Web service-based invocation of business rules.
ILOGJRulesRuleExecutionServer：这是一个符合J2SE和J2EE规范的规则执行环境，包括用于同步、异步和通过Web服务调用业务规则的组件。
However, most of the current rule engines are lack of remote invocation interfaces, so they can't be integrated effectively in the distributed conditions.
然而，当前大多数规则引擎缺少远程调用的接口，在分布式应用方面存在着缺陷，无法被有效地集成。
However, most of the current rule engines are lack of remote invocation interfaces, so they can't be integrated effectively in the distributed conditions.
然而，当前大多数规则引擎缺少远程调用的接口，在分布式应用方面存在着缺陷，无法被有效地集成。
应用推荐