FpML derivatives (Novation request response).
fpml衍生产品(约务更替请求响应)。
The average request response time for 200 concurrent users is 1,381 ms.
对于200个并发用户的平均请求响应时间是1,381ms。
Whether the invocation style is synchronous request response or asynchronous message based.
调用样式是同步请求响应还是基于异步消息。
To which underlying communication and transport protocols can the SAML request response protocol be bound?
SAML请求响应协议可以绑定到哪些底层的通信传输协议？
To complete your understanding of the request response protocol, you need to dig deeper into two different aspects of it.
要彻底理解请求应答协议，则需要深入了解它以下两个不同方面。
The ShippingTask interface needs one request response operation, shipOrder, which takes an Order business object as input.
ShippingTask接口需要一个请求-响应操作shipOrder，该操作以一个Order业务对象作为输入。
Therefore, the IT architect has decided to use a simple request response or callback protocol between the consumer and provider.
因此，IT架构师决定在消费者和提供者之间使用一个简单的请求响应或者回叫协议。
A type property value of 0 references a Refresh Response, and a type property value of 1 references a Request Response.
类型属性值为0的称为刷新响应，类型属性为1的称为请求响应。
When the container invokes the proxy, it passes request, response, and filter chain objects to it.
当容器调用代理时，它将向代理发送请求、响应以及过滤器链对象。
The previous filter in the filter chain passes request, response, and filter chain objects to APF.
过滤器链前面的过滤器将请求、响应和过滤器链对象传递给APF。
In the policy canvas, as shown in Figure 21, you can define message processing request, response, or error rules.
在策略画布中(如图21所示)，您可以定义消息处理请求、响应或错误规则。
Specifically, there are three kinds of handler chains: request, response, and error.
具体来说，有3种句柄链：请求、响应和错误。
Acegi's filter chain proxy invokes SIF and passes request, response, and filter chain objects to it.
Acegi的过滤器链代理调用SIF并向其发送请求、响应和过滤器链对象。
The Web services client invokes the methods of the WS.Handler object on every request, response, and error.
Web服务客户机将针对每个请求、响应和错误调用 WS.Handler对象的各个方法。
Support a variety of interaction styles, such as synchronous request/response, messaging, publish/subscribe, and events
支持多种交互方式，例如同步请求/响应、消息传递、发布/订阅以及事件
Rather than fetching whole Web pages with the traditional request/response models, Ajax applications can asynchronously fetch a small part of a Web page and weave the results into an existing page.
Ajax应用程序可以异步地获得Web页面的一小部分并将结果编织进现有的页面中，而不是用传统的请求/响应模型来获得整个 Web 页面。
This field is used to specify directives that must be obeyed by all caching mechanisms along the request/response chain.
这个字段用于指定所有缓存机制在整个请求/响应链中必须服从的指令。
This is the final request/response portion of the Basic callback scenario described in the WS-I Usage Scenarios document.
这是WS-I使用情形文档中描述的基本回调情形的最后的请求／响应部分。
While sticking with the request/response model, you can use Non-Blocking I/O (NIO) to keep a connection open without wasting waiting threads.
在坚持使用请求/响应模型的同时，您可以使用非阻塞I/O（NIO）来保持连接的打开状态，而不需要浪费等待线程。
However, AJAX still suffers from the limitations of the web’s request/response architecture which prevents servers from pushing real-time dynamic web data.
然而，AJAX仍然受限于web请求/响应架构的弱点，使得服务器不能推送实时动态的web数据。
Two one-way messages can be used to establish request/response communications. To send a SOAP message with SMTP, you will need to perform the following steps
两条单向消息可以用来建立请求／响应通信。
The RMI/IIOP protocol, on the other hand, does have a request/response mechanism so that equivalent requests using RMI/IIOP are served faster than those running over SOAP/HTTP.
另一方面，RMI/IIOP协议则具有请求/响应机制，因此使用 RMI/IIOP 的等效请求要比运行于SOAP/HTTP 之上的请求更快获得响应。
Since this is critical code that you'll use in some form in every Ajax application you write, take a quick tour through what a basic request/response model with Ajax looks like.
因为这段代码非常重要，您编写的每个Ajax应用程序都要以某种形式使用它，先看看 Ajax 的基本请求/响应模型是什么样吧。
Since our scenario called for a form-based application (Microsoft Word) to take part in a request/response handshake, the communication between the initiator and the provider needed to be synchronous.
因为我们的情景需要基于表单的应用程序（MicrosoftWord）参与请求／响应握手，所以启动者与提供者之间的通信必须是同步的。
The ESB is based on a messaging model, so a request/response interaction is handled by two related one-way message flows -- one for the request and one for the response.
此ESB基于消息传递模型，因此由两个相关的单向消息流对请求/响应交互进行处理，一个用于请求，一个用于响应。
HTTP is a request-response application protocol in which the parameters of the request must be set before the request is sent.
HTTP是一种请求-响应式的应用程序协议，必须在请求发送之前设置请求参数。
Semantic web service development should focus on the basic request-response relationship in the communication process.
语义Web服务开发应将重点放在通信过程中的基本请求-响应关系上。
The HTTP protocol has a simple request-response paradigm.
HTTP协议拥有一个简单的请求-响应范式。
WS-BPEL imposes an additional restriction to request-response operations.
WS - BPEL对请求-响应操作施加了其他限制。
This is typically used for synchronous request-response message exchanges.
这通常用于同步请求-响应消息交换。
应用推荐