设置服务请求程序。
For now, assume the requester is a PHP view page.
现在，假定请求者是一个php视图页面。
Step 4 must be performed by the service requester.
步骤4必须由服务请求程序执行。
The response template is returned to the requester.
响应模板返回给请求方。
Such logic can't be reconstructed on the requester side.
这样的业务逻辑无法在请求程序端重新建立。
The requester will then have one fewer thing to worry about.
请求者将因此减少一丝担忧。
Means to invoke both, service provider and service requester.
能调用服务请求者和提供者两者的手段。
You can now deploy the requester to the test environment server.
现在，您可以将该请求者部署到测试环境服务器。
Each software service can act as a service provider or requester.
每个软件服务均可充当一个服务提供者或请求者。
Listing 12 shows the response actually returned to the requester.
清单12显示了实际返回到请求程序的响应。
It then creates and sends back an XRDS document to the requester.
然后，它创建一个XRDS文档并发送回请求者。
The process checks whether the requester is a known customer.
该流程检查请求者是否为已知客户。
Service requester - The client, which binds to a particular service.
服务请求者？客户机，它绑定到特定的服务。
You can consider the Requester side Caching Pattern in this case.
在这个示例中，您可以考虑请求端缓存模式。
GET, where the requester only expects body content in the response.
请求程序仅通过此方法获取响应中的正文内容。
See Resources for the requester-side caching pattern specification.
有关请求端缓存模式规范的信息，请参见参考资料部分。
Now create a business module that represents the requester in Figure 19.
现在创建表示图19中的请求者的业务模块。
The JMS listener then returns the HTTP response to the original requester.
然后，JMS侦听器将HTTP响应返回到原始请求程序。
Effectively, we are putting together some requester logic inside a provider.
有效的方式是将一些请求者逻辑放置在一个提供者中。
The requester USES HTTP to deliver the request and receive any response.
请求程序使用HTTP交付请求并接收任何响应。
The requester then USES this in the correlation ID to filter the response.
请求者随后使用相关ID中的内容对响应进行筛选。
A requester entity USES the Web services functionality with a requester agent.
请求者实体将用请求者代理使用Web服务的功能。
The requester will be bound to the selected service endpoint and then invoke it.
请求者将被绑定到所选的服务端点并随后调用它。
This will install the requester-side caching pattern implementation into RSA.
这会将请求端缓存模式实现安装到 RSA 中。
The service requester needs to set this property value before invoking the service.
服务请求者需要在调用这个服务之前设置这个属性值。
Runtime routing should reflect the geographic affinity between requester and provider.
运行时路由应该反映请求者和提供者之间的地理亲缘关系。
A message may traverse several intermediaries between a requester and a target service.
消息可能会通过请求者和目标服务之间的若干中介。
The service requester interacts with the service realization to achieve a business task.
服务请求者通过与服务实现进行交互来完成业务任务。
See figure 7 message topology view for the result of selecting message from requester side.
参见 “图7.消息拓扑视图”，显示了选择来自请求者端的消息的拓扑。
应用推荐