er - one of the hardest things I struggle with is names for classes.
A conduit subscription ensures that only subscriber object is passed
between a network connection for a matching subscription, as opposed
to all subscriptions being propagated - which for Topics could
(would) result in duplicate messages being passed across the network,
one for every subscriber - not good. The only situation where you
wouldn't use a Conduit is if you wanted evenly balanced Queues across
networks, but to avoid duplicates, the messages sent would need to be
non-persistent.
cheers,
rob
On 4 Jan 2007, at 11:53, stephans wrote:
Hello everybody,
I am struggling with some of the configuration parameters. Could
anybody
please outline what "Conduit
Subscriptions" are all about? All I have found in the documentation
is the
line
"multiple consumers subscribing to the same destination are treated
as one
consumer by the network"
Can anybody emphasize this topic?
Thank you very much in advance, I appreciate your answers.
Greetings,
Stephan
--
View this message in context: http://www.nabble.com/Concept-of-%
22conduit-subscriptions%22-tf2919054.html#a8157889
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
