当事件发布者与事件接收者位于不同层时，发生垂直因果关系。
Vertical causality occurs when the event publisher resides on a different layer than the event receiver.
无耦合的关联：事件发布者和事件订阅者预先无需知道彼此的存在。
Decoupled associations: event publishers and event subscribers don't need to know the existence of each other beforehand.
在这些小节中定义的事件框架包括事件通道、事件发布者和事件接收者。
The event framework defined in these sections consists of an event channel, event publishers, and event receivers.
事件通道是事件发布者用于发布事件，事件接收者用于订阅和接收事件的组件。
An event channel is a component that event publishers use to publish events and that event receivers use to subscribe and receive events.
当事件发布者与事件接收者位于架构虚拟层中的同一层时，发生水平因果关系。
Horizontal causality occurs when the event publisher resides on the same layer in an architecture's virtual layers as the event receiver.
随着消息被分发给收件人，SametimePostService将根据结果更新事件发布者(参见下面的代码片段)。
As the message gets delivered to recipients, Sametime Post Service keeps the event publisher updated about the results (see the following code snippet).
publish访问与相关发布者构件事件之间的联系。
Linking of the dojo.publish calls to the event of the relevant publisher component.
几乎所有组件都必须处理事件，要么作为事件的发布者，要么作为事件的处理者。
Nearly all components must deal with events, either as an event publisher or as an event handler.
最初，事件的接收者通过调用订阅方法向发布者声明他的兴趣。
Initially, the receiver of the event declares its interest to the publisher by calling the subscribe method.
发布者通常与外部信息和事件源存在接口，并将有关事件打包到一条通知消息中。
A publisher typically interfaces to external information and event sources and packages the pertinent event in a notification message.
随着事件的发生，发布者通过回调过程将通知发送给订阅者。
As events occur, the publisher sends them to subscribers via a callback procedure.
底层消息传递或事件基础结构负责将主题从发布者传递到订阅者。
The underlying messaging or event infrastructure is responsible for delivery from publisher to subscribers.
为了完成该操作，订阅者Portlet对该话题注册了其事件处理器，而发布者 Portlet （图9）就会对该话题发布一条信息。
To accomplish this, the subscriber portlet registers its event handler to this topic, and the publisher portlet (Figure 9) publishes a message to this topic.
这个发布者接着使用普通的。NET事件语义来引发事件并且调用订阅者。
The publisher then fires the event using normal. NET eventing semantics and the subscriber is called.
这个发布者接着使用普通的。NET事件语义来引发事件并且调用订阅者。
The publisher then fires the event using normal. NET eventing semantics and the subscriber is called.
应用推荐