Invocation style depends on the source component.
调用样式取决于源组件。
Special behaviour of the invocation style within a Fan Out or Fan in primitive.
FanOut或FanIn原语中调用样式的特殊行为。
This is a typical invocation style in an SOA environment with messaging middleware.
这是具有消息传递中间件的SOA环境中的典型调用方式。
If the reference is w-typed then the only invocation style available to the user is DII.
如果引用是w - typed的，则用户唯一可用的调用样式就是DII。
Whether the invocation style is synchronous request response or asynchronous message based.
调用样式是同步请求响应还是基于异步消息。
This introduces a significant point: When a service is designed, what determines the invocation style to be used?
这就引入了一个重要的问题：设计服务时，什么决定了所使用的调用方式？
The only exception to this rule is when a mediation flow component is called using the invokeAsyncWithCallback invocation style.
此规则唯一的例外是使用invokeAsyncWithCallback 调用样式调用中介流组件时。
Asynchronous: Indicates the preferred invocation style is either asynchronous with deferred response or asynchronous with callback.
异步：指示首选的调用样式是带有延迟响应的异步调用或带有回调的异步调用。
As above, all asynchronous invocations are made using the async with callback invocation style, never asynchronous deferred response.
如上所述，所有异步调用都是使用asyncwith callback调用样式进行的，而不使用异步延迟响应。
The invocation style used by the mediation flow component for service invocations with a service Invoke primitive is determined by three factors.
中介流组件对具有一个服务调用原语的服务调用使用的调用样式由以下三个因素决定。
Representational State Transfer (REST) is a software architecture pattern and invocation style for accessing and updating resources on a network.
具象状态传输(Representational State Transfer,REST)是用于访问和更新网络资源的软件架构模式和调用样式。
This article explains how to set or determine which invocation style will be used at runtime, based on specific characteristics of your application.
本文将说明如何在运行时基于应用程序的具体特征设置或确定将使用哪个调用样式。
They require very little configuration and use different transports depending on the client invocation style (synchronous, asynchronous, and so on).
它们几乎不需要进行配置，它们根据客户端的调用样式(同步、异步等等)来使用不同的传输方法。
You might need to promote properties that enable administrative control over, for example, invocation style, alternate routing, and retry configuration.
您可能需要提升那些能够对调用方式、备选路由和重试配置等等启用管理控制的属性。
The invocation style that the mediation flow component sees is partly determined by the binding used on the mediation module export that receives the request.
中介流组件看到的调用样式部分由接收请求的中介模块导出上使用的绑定决定的。
Invocation style: to apply the pattern, the invocation style should be request and response, where one response message is generated according to one request.
调用样式：要应用该模式，调用样式应为请求-响应样式，应根据一个请求生成一个响应消息。
Use the information here to ensure that your application USES the appropriate invocation style based on your service endpoints, performance requirements, and so forth.
使用本文的信息可确保应用程序基于服务端点、性能需求等使用相应的调用样式。
First, remember that much of the power of actors comes from the message-passing style rather than the blocking-invocation style that characterizes the rest of the imperative programming world.
首先，actor的主要能力来源于消息传递风格，而不采用阻塞-调用风格，这是它的主要特点。
The previous discussion Outlines two basic rules invocation styles (synchronous request-response style and asynchronous event-handling style) and distinguishes stateless versus stateful processing.
前面的讨论中给出了两个基本规则调用样式(同步请求-响应样式和异步事件处理样式)并对无状态处理和有状态处理进行了区分。
Now you understand the connectivity style choices for service invocation.
现在，您了解了服务调用的连接方式选择。
Now that you understand the consumer's choices for service invocation communication style, take a look at the consumer's connectivity style choices for connecting to a provider.
既然您了解了使用者对服务调用通信方式的选择，就可以看一看使用者对用于连接到提供者的连接方式的选择。
Based on these policies and desired interaction style, an appropriate endpoint address for the service invocation can be selected and the request can be routed appropriately.
基于这些策略和期望的交互类型，服务调用的一个适合的端点地址将被选择，从而请求将被正确的路由。
Based on these policies and the desired interaction style, an appropriate endpoint address for the service invocation can be selected, and the request can be routed appropriately.
基于这些策略和期望的交互类型，服务调用的一个适合的端点地址将被选择，从而请求将被正确的路由。
The service Invoke primitive has a property that, when specified, prevents the mediation flow component from using the asynchronous with callback style for the service invocation.
服务调用原语具有一个属性，在指定该属性时，可以防止中介流组件对服务调用使用带有回调的异步调用样式。
In the interest of simplicity, it is good practice to have a single invocation API style that is capable of invoking services with other protocols.
出于对简单性的需求，能够使用其他协议调用服务的单一调用api样式是一个很好的实践。
In the near future this multi-protocol style will allow service invocation using RMI over IIOP, resulting in efficient interaction with EJB services.
在不久的将来，这种多重协议样式将允许使用IIOP上的RMI进行服务调用，以使EJB服务实现有效的互操作。
If a dynamic endpoint is used in the mediation flow, the preferred interaction style is derived from a default import wired to the reference used for the dynamic invocation.
如果在中介流中使用动态端点，则从连接到用于动态调用的引用的缺省导入生成了首选交互样式。
Request-response style -- synchronous invocation by client services.
请求-响应样式——由客户机服务进行同步调用。
This allows remote Method Invocation (RMI) -style remote exceptions to be implemented using SOAP.
这允许使用SOAP来实现RMI风格的远程异常。
However, although the Web service infrastructure may encapsulate details of invocation and hence simplify code, the service design should be influenced by the style of invocation.
不过，虽然Web服务基础结构可以封装调用的细节，从而简化代码，但服务设计也应对调用方式加以考虑。
应用推荐