设置服务请求程序。
For now, assume the requester is a PHP view page.
现在，假定请求者是一个php视图页面。
Step 4 must be performed by the service requester.
步骤4必须由服务请求程序执行。
Such logic can't be reconstructed on the requester side.
这样的业务逻辑无法在请求程序端重新建立。
The requester will then have one fewer thing to worry about.
请求者将因此减少一丝担忧。
You can now deploy the requester to the test environment server.
现在，您可以将该请求者部署到测试环境服务器。
Each software service can act as a service provider or requester.
每个软件服务均可充当一个服务提供者或请求者。
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.
在这个示例中，您可以考虑请求端缓存模式。
There are two kinds of people in the world: requester and giving.
世界上有两种人：取者和给予者。
The requester USES HTTP to deliver the request and receive any response.
请求程序使用HTTP交付请求并接收任何响应。
You can choose to display topology from Requester side or Provider side.
您可以选择从requester方或provider方显示拓扑。
You can use the Requester Side Caching Pattern to implement the On Write policy.
您可以使用请求端缓存模式来实现写策略。
See figure 7 message topology view for the result of selecting message from requester side.
参见 “图7.消息拓扑视图”，显示了选择来自请求者端的消息的拓扑。
These statements suggest "service" is a physical thing with which a requester can interact.
这些话表明“服务”是某种物理的东西，请求者可以与之交互。
The original requester will use a activity to consume the response delivered by the activity.
原始请求者将使用活动来消费由活动传递的响应。
Like a class object, the requester application is capable of treating the service as one.
如同类对象，请求者应用程序能够将服务看作是一个整体。
Like a class object, the requester application is capable of treating the service as one.
如同类对象，请求者应用程序能够将服务看作是一个整体。
应用推荐