1·To do so, the service provider must have a way to communicate back with the service requester.
要实现这一点，服务提供者必须有返回途径与服务请求者进行通信。
2·Response includes attribute assertions for those attributes for which the requester has permissions.
响应中包括请求者拥有权限的那些属性的属性断言。
3·You have now secured both the requester and the provider with LTPA token at the message level.
您现在已经使用ltpa令牌在消息级别上确保了请求者和提供者的安全。
4·If a change is made to any aspect of a service that is coupled, then either the requester or the provider application code (or, more likely, both) will have to change.
如果耦合的服务任何方面有所变化，那么，请求者或提供者的应用程序代码(更可能是两者同时)必须改变。
5·Means to invoke both, service provider and service requester.
能调用服务请求者和提供者两者的手段。
1·New levels of dynamic behavior can be achieved, because the ESB can enforce policy in real time for each interaction between requester and provider.
可以实现新级别的动态行为，因为ESB能够为请求程序和提供程序之间的每个交互实时执行策略。
2·With examples, this article illustrates how you can offer a service to a requester in a different protocol than the service provider expects.
本文通过一些示例说明，如何使用与服务提供程序预期不同的协议向请求程序提供服务。
3·Set up the service requester.
设置服务请求程序。
4·Using a particular software pattern asset, the requester side cache, as an example we will detail use usage patterns and best practices when using the RAM Rich Client.
在使用ram富客户端时，我们将详细介绍如何使用用法模式和最佳做法，例如，使用特定的软件模式资产和请求程序端缓存。
5·The mediation flow component established between the service requester and the service provider is straightforward and simply logs all messages that come across to a database.
在服务请求程序和服务提供程序之间建立的中介流组件非常直观，并简单地记录了通过数据库的所有消息。