Type	NEW
Priority	HIGH
Status	CLOSED

Topic	Published messages without a qos <destination> tag are published in Publish/Subscribe mode
Des cription	If you publish a message using the publish() message, it is sent to xmlBlaster only. Interested client may access this message using the synchronous get() or the asynchronous subscribe() method. This is called the Publish/Subscribe pattern, which allows a maximum decoupling of distributed components. Note that if a subscriber callback fails, the publisher won't notice this.
Example Java	<qos> <!-- no <destination> specified! --> </qos>
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.forceUpdate
See REQ	engine.qos.publish.persistent
See REQ	engine.qos.publish.isVolatile
See REQ	engine.qos.publish.readonly
See REQ	engine.queue
See REQ	mime.plugin.publishfilter
See API	org.xmlBlaster.client.qos.PublishQos
See API	org.xmlBlaster.client.key.PublishKey
See TEST	org.xmlBlaster.test.qos.TestPub

This page is generated from the requirement XML file xmlBlaster/doc/requirements/engine.qos.publish.PubSub.xml

Back to overview