1.The service requester and the mediation flow component itself did not change at all, hence no programming was involved.
服务请求者和中介流组件本身根本不会发生改变，因此不涉及到编程工作。
2.For the next purchase, the requester can receive an incentive in accordance with the point and enjoy a special service such as a discount.
在下回购买时委托者就能够依照该积分得到奖励，享受减价等的优惠。
3.What would a WebSphere ESB custom mediation primitive look like that logs the name of the requester for a given service?
用于记录给定服务的请求方的名称的WebSphereESB自定义中介元素是什么样？
4.The communication between service requester and service provider sets up the basic relationship in a web service: request and response.
服务请求程序和服务提供程序之间的通信建立了Web服务中的基本关系：请求和响应。
5.When execution is done, a message might be send to the requester that the works done, and this might be accompanied by some data.
在执行完成后，可能会发送给请求者一条工作已完成的消息，并伴随有一些数据。
6.The requester then invokes the WS response template implementation with a key and a request template.
然后，请求者将使用密钥和请求模板来调用WS响应模板实现。
7.In case of a requester-server channel, the receiving system (store server) initiates the connection.
在请求方-服务器通道中，接收系统（零售店服务器）发起连接。
8.The idealized SOA is shown in Figure 1, where a requester interacts with a provider to achieve some business-relevant task.
理想的SOA如图1所示，在这种架构中，请求者通过与提供者交互，完成某个与业务相关的任务。
9.These statements suggest "service" is a physical thing with which a requester can interact.
这些话表明“服务”是某种物理的东西，请求者可以与之交互。
10.Now if the requester_s system crashes at any time the requester will know where to restart by the records it keeps in its local database.
现在如果请求方的系统在任何时候崩溃了，那么请求方总能通过它保存在本地数据库里的记录找到重新开始的位置。