消息内容的格式必须得到消息发布者和订阅者的同意和理解。
The format of the message content must be agreed and understood by both publishers and subscribers.
订阅者是消息使用者，其接收特定主题下由消息发布者发布的消息。
A subscriber is a message consumer that receives messages under a particular topic, published by a message publisher.
通知代理：不会创建通知消息，但代表一个或多个发布者管理通知流程。
Notification Broker: Does not create notification messages, but manages the notification process on behalf of one or more publishers.
发布者通常与外部信息和事件源存在接口，并将有关事件打包到一条通知消息中。
A publisher typically interfaces to external information and event sources and packages the pertinent event in a notification message.
在某个时间，发布者发布时间轴服务已经订阅的通知消息。
At some time the publisher publishes a notify message that the Timeline service has subscribed to.
发布者：创建通知消息的实体。
Publisher: an entity that creates notification message instances.
在第32行，使用主题发布者向主题队列发布消息。
In line 32 you use the topic publisher to publish the message to the topic queue.
随着消息被分发给收件人，SametimePostService将根据结果更新事件发布者(参见下面的代码片段)。
As the message gets delivered to recipients, Sametime Post Service keeps the event publisher updated about the results (see the following code snippet).
具有带Web服务SOAPover JMS绑定的导入的模块是在该主题下发布消息的发布者。
A module that has an import with a Web service SOAP over JMS binding is a publisher that publishes a message under the topic.
发布者对象创建一个SametimePost对象，然后设置其标题、消息正文以及收件人(参见下面的示例代码)。
The publisher object creates a Sametime Post object, and then sets its title, message body, and recipients (see the following code sample).
如果您使用与测试原始发布者模块相同的方式测试请求者模块，您将看到Subscriber1和Subscriber2都收到了由请求者发送的消息。
If you test the requester module in the same way you tested the original publisher module, you'll see that both Subscriber1 and Subscriber2 get the message sent by the requester.
您应该看到如图18中所示的内容。控制台的输出显示两个订阅者都收到了由发布者发送的消息。
You should see something like Figure 18. The output in the console shows that both subscribers got the message sent by the publisher.
发布者将这条消息发送到通知代理。
The publisher sends this message to the notification broker.
发布者的代码与点到点应用程序的对应项完全一样，这是因为JMS 1.1API允许使用可以产生发布到队列和主题的消息的JMS代码。
The code for the publisher is identical to that of the point-to-point application, because the JMS 1.1 API enables JMS code that can produce messages onto either a queue or a topic.
要谨记，应用程序不能发布到主题名称中包含通配符的JMS主题，因为发布者只能将消息发布到单个主题。
Keep in mind that an application cannot publish to a JMS topic whose topic name contains wildcards, because a publisher can only publish a message to a single topic.
订阅者在一个特定的主题中注册它们的兴趣，而发布者则说明与其消息相关的主题。
Subscribers register their interest in a particular topic, and publishers indicate the topic relevant to their messages.
发布者通常向消息添加一个主题头部，根据通知的主题模型或分类模式确定该消息的类别。
Publishers typically add a topic header to the message that classifies the message according to the topic model or classification scheme of the notifications.
底层消息传递或事件基础结构负责将主题从发布者传递到订阅者。
The underlying messaging or event infrastructure is responsible for delivery from publisher to subscribers.
消息：从发布者那里接收到的有效的消息载体。
Message: the payload (body) of the message, as received from the publisher.
对内容发布者来说，Google此举显然不是一个好消息，因为他们需要精确地统计数据管理自己的网站，进而调整自己的营销策略。
For publishers, this is obviously not an ideal situation, as they rely on accurate statistics to manage their sites and tweak their marketing efforts.
当谈及Facebook时，Buch了解到大多数成功的信息发布者不仅仅只是发消息，他们也分享一点'亲密'。
When talking to Facebook, Buch learned that the most successful publishers were doing more than posting stories, they were using it as a way to share a little more 'intimately.'
WS -BrokersNotification：此规范允许非web服务实体创建一个发布者，此发布者会创建消息，并通过一个名为NotificationBroker的单独代理服务分发这些消息。
WS-BrokersNotification: This specification allows a non-Web service entity to create a publisher that creates messages and distributes them through a separate broker service called NotificationBroker.
DB 2和OracleWeb服务都是发布者，向主题的所有订阅者发送包含该主题的信息的警报和消息。
DB2 and Oracle Web services are each a publisher sending alerts and messages containing information about a topic to all subscribers to that topic.
这个应用程序场景适用于发布者和订阅者模型，以便它们可以使用WebSphereMQ资源通过SOAP消息进行通信。
This application scenario is designed for both a publisher and a subscriber so that they can use WebSphere MQ resources to communicate with SOAP messages.
多对多消息传递的一个很好的例子就是e -mail listserve：多个发布者可以将多条消息投递到一个主题，而所有的订阅者将获取每一条消息。
A good example of many-to-many messaging would be an E-mail listserve: multiple publishers can post messages on a topic, and all subscribers will receive each message.
主题连接工厂用于发布者的Web服务SOAPoverJMS导入绑定，使其创建到SIBus jms提供者的连接以发布消息。
The topic connection factory is used for the publisher's Web service SOAP over JMS import binding to make a connection to the SIBus JMS provider to publish messages.
PubSubRealTime应用程序创建了一个JMS发布者和订阅者，其中发布者发送一组消息，然后由订阅者接收。
The PubSubRealTime application creates a JMS publisher and subscriber — the publisher sends a set number of messages that are then received by the subscriber.
消息的发布者能够使用通用接口发送数据，中间代理负责数据的分发与接受，消息的接收者能够使用通用接口读取数据。
Publishers can publish data using universal interfaces, and the agent layer is responsible for sending and receiving message, and subscribers can read their massage through universal interfaces.
消息的发布者能够使用通用接口发送数据，中间代理负责数据的分发与接受，消息的接收者能够使用通用接口读取数据。
Publishers can publish data using universal interfaces, and the agent layer is responsible for sending and receiving message, and subscribers can read their massage through universal interfaces.
应用推荐