英语翻译4.0 Data and Message Exchange Patterns for Enterprise SO

英语翻译
4.0 Data and Message Exchange Patterns for Enterprise SOA
The most basic message exchange pattern is a common Request-Response where the parties can simply communicate with each other.This is the basic building block of most SOA interactions and is depicted below.
4.1 Request-Response
Request-Response is a pattern in which the service consumer uses configured client software to issue an invocation request to a service provided by the service provider.The request results in an optional response,as shown in Figure 4-1.
4.2 Request-Response via Service Registry (or Directory)
An optional service registry can be used within the architecture to help the client automatically configure certain aspects of its service client.The service provider pushes changes regarding the service’s details to the registry to which the consumer has subscribed.When the changes are made,the service consumer is notified of these changes and can configure its service client to talk to the service.This is represented conceptually in Figure 4-2.
4.3 Subscribe-Push
A third pattern for interaction is called Subscribe-Push,shown in Figure 4-3.In this pattern,one or more clients register subscriptions with a service to receive messages based on some criteria.Regardless of the criteria,the externally visible pattern remains the same.
Subscriptions may remain in effect over long periods before being canceled or revoked.A subscription may,in some cases,also register another service endpoint to receive notifications.For example,an emergency management system may notify all fire stations in the event of a major earthquake using a common language such as the OASISxv Common Alerting Protocol (CAP)
Note that this pattern can be triggered by a multitude of events.In figure 4-3,an auditable event is triggering a message being sent to a subscribed client.The trigger could be a service consum- er’s action,a timeout action,or a number of other actions that are not listed in the example above.Each of these represents a specialization of the Subscribe-Push pattern.
----------

正在翻译中,人译需要时间,不要给分给那些机译的.
4.0 Data and Message Exchange Patterns for Enterprise SOA
4.0 针对企业SOA的数据和信息交换模式(SOA:service-oriented architecture面向服务架构)
The most basic message exchange pattern is a common Request-Response where the parties can simply communicate with each other. This is the basic building block of most SOA interactions and is depicted below.
最基本的信息交换模式就是通常的"要求-反应",即各个组件能简单地彼此交流信息.这是大多数SOA交互服务的基本构件.如下述.
4.1 Request-Response
4.1 要求-反应(或请求-响应)
Request-Response is a pattern in which the service consumer uses configured client software to issue an invocation request to a service provided by the service provider. The request results in an optional response, as shown in Figure 4-1.
"要求-反应"模式就是服务消费者使用配套的客户端软件发送一条调用指令到服务供应商的服务器,然后得到可选回应,如图4-1所示.
4.2 Request-Response via Service Registry (or Directory)
4.2 经由服务注册表(或索引)的"要求-反应"
An optional service registry can be used within the architecture to help the client automatically configure certain aspects of its service client. The service provider pushes changes regarding the service’s details to the registry to which the consumer has subscribed. When the changes are made, the service consumer is notified of these changes and can configure its service client to talk to the service. This is represented conceptually in Figure 4-2.
在架构内,可以用一个可选的服务注册表,帮助客户自动配置其服务客户端的某些选项.服务提供商将显示相关细节变化对话框,推(弹出)给那些已经订阅的消费者.当改变出现时,服务消费者会得到通知,并配置其服务客户端与服务器进行对话.概念上的描述见图4-2.
4.3 Subscribe-Push
4.3 订阅-推
A third pattern for interaction is called Subscribe-Push, shown in Figure 4-3. In this pattern, one or more clients register subscriptions with a service to receive messages based on some criteria. Regardless of the criteria, the externally visible pattern remains the same.
第三种交互模式叫"订阅-推",如图4-3.在这种模式中,一个或者多个客户注册使用订阅,这种订阅服务可以收到基于某些条件的消息.如果不考虑条件,终端上显示的模式保持不变.
Subscriptions may remain in effect over long periods before being canceled or revoked. A subscription may, in some cases, also register another service endpoint to receive notifications. For example, an emergency management system may notify all fire stations in the event of a major earthquake using a common language such as the OASISxv Common Alerting Protocol (CAP)
实际上,订阅会一直保留下来,直到被取消或撤回.在某些情况下,订阅也可以显示收到别的服务端的通知内容.例如,在一次严重的地震中,紧急事故管理系统可以通知所有的消防站,用的是一种通用的语言,比如OASIS(结构化信息标准促进组织)的通用预警协议(CAP).
Note that this pattern can be triggered by a multitude of events. In figure 4-3, an auditable event is triggering a message being sent to a subscribed client. The trigger could be a service consum- er’s action, a timeout action, or a number of other actions that are not listed in the example above. Each of these represents a specialization of the Subscribe-Push pattern.
注意到这个模式会被多种事件触发,在图4-3中,一起审核事件触发一条信息被送达一个客户端.触发可能是一次服务消费者的动作,或是一次超时动作,或者其他在上述例子中没有列出的动作.每一个动作都表述了一种特殊的"订阅-推"模式.