Messaging-config.xml: Defines publish-subscribe messaging information.
messaging - config . xml：定义发布-订阅消息传送信息。
A service can have many types of MEPs: one-way, publish-subscribe, or request-response.
服务可以具有很多类型的mep：单向、发布-订阅或请求-响应方式。
JMS defines two modes of messaging: point-to-point (P2P) and publish-subscribe (pub-sub).
JMS定义了两种信息传递模式：点对点(p 2 p)和发布—订阅(pub - sub)。
The Publish-Subscribe design pattern taught us how to manage events without broadcasting them.
发布-订阅(Publish - Subscribe)设计模式指导我们如何在不广播事件的情况下管理它们。
The former are used for point-to-point messaging and the latter in publish-subscribe scenarios.
前者用于点对点消息，后者用于发布-订阅场景。
This style is similar to the Observer pattern in that it promotes a publish-subscribe way of working.
这个风格与Observer模式十分相似，因为它促进一种发布-订阅的工作方式。
In the enterprise integration domain, you might have guaranteed delivery and publish-subscribe patterns.
在企业整合领域中，您可以保证交付和发布订阅模式。
Messaging middleware supports multiple messaging paradigms: request-response, publish-subscribe, and one-way.
消息中间件支持多种消息传递范例：请求-响应、发布-订阅和单向方式。
An alternate model describing how multiple applications interact over the JMS API is called the publish-subscribe model.
另一个描述多个应用程序如何在JMSAPI上进行交互的模型被称为发布-预定(publish - subscribe)模型。
The Swing framework makes extensive use of the Observer pattern (also known as the publish-subscribe pattern) in the form of event listeners.
Swing框架以事件侦听器的形式广泛利用了观察者模式(也称为发布-订阅模式)。
The Dojo toolkit provides a publish-subscribe mechanism that enables the creation of loosely coupled components in a client-centric application.
DojoToolkit提供了一个“发布-订阅”机制，该机制支持在一个以客户为中心的程序之中创建松散耦合的构件。
There are several SOA interaction paradigms in common use including document centric messaging, remote procedure calls (RPC), and publish-subscribe.
在普通的使用，包括文件中心信息、远程程序调用(rpc)以及发布订购中，有一些SOA交流形势图。
When you have to notify multiple object managers of an event at the same time, a publish-subscribe paradigm is best suited for your communication needs.
如果必须将一个事件同时通知多个对象管理器，那么使用发布-订阅模型是最合适的。
Allows processes to register with a "cloud" to be notified of updates to the channel, implementing a lightweight publish-subscribe protocol for RSS feeds.
允许进程注册为“cloud”，频道更新时通知它，为rss提要实现了一种轻量级的发布-订阅协议。
Laharsub is an open source.net publish-subscribe message server for real time web applications like chat, online collaboration, news or stock trade updates, etc.
Laharsub是一种开源的。NET发布-订阅消息服务器，用于实时的web应用程序，像聊天、在线写作、新闻或者股票交易更新等等。
In publish-subscribe interactions, an event published once may be acted upon by multiple subscribers; subscribers may filter incoming events by topic using selectors.
在发布-订阅交互中，一次发布的事件可能作用于多个订户；订户可以使用选择器筛选主题传入的事件。
When integrating various applications, some may need to work in the event-processing mode, which might mandate support for a publish-subscribe style of message exchange.
与各种应用程序进行集成时，有些可能需要采用事件处理模式工作，而此模式要求必须支持发布-订阅样式的消息交换方式。
From the JMS perspective, as mentioned earlier, one of the most prominent changes has been to combine point-to-point messaging and publish-subscribe into a single domain.
如前所述，从JMS角度看，最显著的更改之一是将点到点的消息和发布-订阅合并到单个域。
In short, MOM excels in providing asynchronous communication between processes, publish-subscribe (one-to-many) message delivery semantics, and high levels of reliability.
简而言之，MOM擅长于提供流程间的异步通讯、发布-订阅(一对多)消息来传递语义和保证高可靠性。
Publish-Subscribe Notification for Web services: This specification sets the goals and requirements for the WS-Notification family of documents and includes security consideration.
Publish - SubscribeNotificationforWebservices：此规范为WS - Notification文档系列设置目标和需求并包括安全注意事项。
The exchange of information is done by using a data-centric publish-subscribe architecture that loosely couples components, thereby enabling anonymous exchange of data between disparate systems.
信息的交换是使用数据中心的结构完成的，该结构有松散耦合的构件，因此支持在分隔系统之间交换数据。
Publish/subscribe in this context means the decoupling of producers and consumers: producers do not need to know based on what criteria consumers will receive messages.
本文中区别发布/订阅是为了将生产者和消费者拆分开来：生产者无需知道消费者按照什么标准接受消息。
We then look at publish/subscribe messaging and how it may be used to connect any number of applications together.
接下来介绍发布/订阅消息传递以及如何利用它将任意数量的应用程序连接在一起。
The build process creates some artifacts that need to be modified to use the publish/subscribe messaging model.
构建过程将创建一些构件，需要修改这些构件才能使用发布/订阅消息模型。
When using the publish/subscribe model, many applications might be receiving request messages.
当使用发布/订阅模型时，可能有许多应用程序在接收请求消息。
The Service Integration Bus enables us to integrate applications in a variety of ways, including the ability to build publish/subscribe messaging applications.
服务集成总线允许采用各种方式集成应用程序，包含了构建发布/订阅消息传递应用程序的功能。
Once that is done, we will set up the publish/subscribe broker to start and end under control of the queue manager.
完成此任务后，我们将设置在队列管理器控制下开始和结束的发布/订阅代理。
This protocol follows the topic based publish - subscribe scheme.
这个协议遵循基于主题的发布——订阅机制。
Message exchange pattern: data services could be accessed via the four primary message exchange patterns - request/reply (tight SLA), request/reply (relaxed SLA), fire/forget, and publish/subscribe.
消息交换模式：数据服务可以通过四种主要的消息交换模式被访问：请求-应答（严格SLA）、请求-应答（宽松SLA ），即发即弃和发布-订阅。
With this peer to peer style, a publish/subscribe system can be created.
使用这种对等风格，可以创建发布/订阅系统。
应用推荐