xmlBlaster - Requirement mom.publishsubscribe

REQUIREMENT

mom.publishsubscribe

Type NEW

Priority HIGH

Status CLOSED

Topic XmlBlaster supports the publish/subscribe paradigm

Des
cription
XmlBlaster allows clients to independently publish messages. Clients may subscribe independently to messages.

The indirect communication, in particular the publish/subscribe communication model, is gaining increasing acceptance as a useful alternative to direct communication models, such as the ones based on remote invocations.

The main advantage of this paradigm is that it supports a weak coupling among participants, which do not need to be aware of the location or number of its peers. This simplifies the reconfiguration of the applications and eases the reuse of the same components for different applications.

One of the main advantages of the publish/subscribe model is that it decouples publishers and subscribers in several dimensions. Note these three dimensions of decoupling:

Space decoupling:
That captures the fact that interacting parties do not need to known each other

Time decoupling:
That captures the fact that parties do not need to be actively participating in the interaction at the same time

Flow decoupling:
That captures the asynchrony of the model

Typically publish/subscribe behavior is configurable with quality-of-service (QoS) parameters, for example:

Message reliability

Message expire time

Message ordering

Message priority

Message filtering

Message checking

Message manipulation

Message latency

Message compression

Routing of messages

Readonly messages

Example
Java

Configure
NOTE: Configuration parameters are specified on command line (-someValue 17) or in the xmlBlaster.properties file (someValue=17). See requirement "util.property" for details.
Columns named Impl tells you if the feature is implemented.
Columns named Hot tells you if the configuration is changeable in hot operation.

See REQ engine.qos.publish.PubSub

This page is generated from the requirement XML file xmlBlaster/doc/requirements/mom.publishsubscribe.xml

Back to overview

Topic	XmlBlaster supports the publish/subscribe paradigm
Des cription	XmlBlaster allows clients to independently publish messages. Clients may subscribe independently to messages. The indirect communication, in particular the publish/subscribe communication model, is gaining increasing acceptance as a useful alternative to direct communication models, such as the ones based on remote invocations. The main advantage of this paradigm is that it supports a weak coupling among participants, which do not need to be aware of the location or number of its peers. This simplifies the reconfiguration of the applications and eases the reuse of the same components for different applications. One of the main advantages of the publish/subscribe model is that it decouples publishers and subscribers in several dimensions. Note these three dimensions of decoupling: Space decoupling: That captures the fact that interacting parties do not need to known each other Time decoupling: That captures the fact that parties do not need to be actively participating in the interaction at the same time Flow decoupling: That captures the asynchrony of the model Typically publish/subscribe behavior is configurable with quality-of-service (QoS) parameters, for example: Message reliability Message expire time Message ordering Message priority Message filtering Message checking Message manipulation Message latency Message compression Routing of messages Readonly messages
Example Java
Configure	NOTE: Configuration parameters are specified on command line (-someValue 17) or in the xmlBlaster.properties file (someValue=17). See requirement "util.property" for details. Columns named Impl tells you if the feature is implemented. Columns named Hot tells you if the configuration is changeable in hot operation.
See REQ	engine.qos.publish.PubSub