HTTP request and response headers.
HTTP请求和响应消息头。
Invocation vs. request and response.
调用vs请求和响应。
Here are the sample request and response.
下面是示例请求和响应。
Below are the sample request and response.
下面是示例请求和响应。
Measure the size of the request and response.
测定请求和响应的大小。
HTTP request and response headers for static files.
用于静态文件的HTTP请求和响应头。
Figure 7 shows a sample request and response message.
图7展示了一个样本请求和响应消息。
Essentially, what is the request and response protocol?
基本上而言，请求和响应协议是什么？
Notice that it logs both request and response messages.
注意，它同时记录请求消息和响应消息。
Both request and response are wrapped in SOAP envelopes.
请求和响应都被包装在soap封包中。
API transactions consist of an HTTP request and response.
API事务由一个HTTP请求和响应组成。
Listings 2 and 3 highlight the HTTP request and response.
清单2与3显示了HTTP请求与响应。
Requires an XML wrapper around every request and response.
每个请求和响应都需要一个XML包装器。
Like a servlet, it receives a request and response object.
像servlet一样，它接受请求并响应对象。
A sample request and response for each service are also listed.
还会列出针对每种服务的示例请求和响应。
It's a map showing where the request and response went in the SOA.
它是说明请求响应在何处进入SOA的图像。
JNDI resources for both request and response connection factories.
同时用于请求和响应连接工厂的JNDI资源。
For each executed operation, there is a request and response entry.
对于每个已执行的操作，都有一个请求和响应条目。
Only the ESB knows where to route the request and response messages.
只有ESB知道将请求和响应消息路由到何处。
This enables the request and response messages to be linked together.
这就将请求消息和相应消息链接到一起。
Exposing the hidden information through semantic request and response.
通过语义请求和响应公开隐藏信息。
Hiding the implementation details through semantic request and response.
通过语义请求和响应隐藏实现细节。
The time for marshalling and unmarshalling the request and response.
打包和解包请求和应答所需的时间。
StringHttpMessageConverter Read/write a string from request and response.
StringHttpMessageConverter从请求和响应读取/编写字符串。
When you expand them, you can see the request and response data in each page.
当您展开它们时，您会在每一个页面中看到请求和响应数据。
The request framework manipulates and transforms request and response messages.
请求框架(Request framework)操纵和转换请求和响应消息。
The LDAP protocol defines request and response messages for directory operations.
LDAP协议定义了目录操作的请求和响应消息。
The handler interface is oriented toward processing request and response messages.
处理程序接口则是面向处理请求消息和响应信息的。
Sometimes, to test your controller, you need access to the raw request and response.
有时，要测试控制器，您需要访问原始的请求和响应。
The service controller ACTS as an entry point of the request and response framework.
服务控制器作为请求和响应框架的入口点。
应用推荐