Unless you're using Multicast right? I hope so, because our testing with
SwiftMQ 2.0.1 led us to this conclusion.
Trent
-----Original Message-----
From: Andreas Mueller [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, 6 June 2001 11:39 PM
To: [EMAIL PROTECTED]
Subject: [developers] Topic question
> I plan on defining a different topic at each router because I only need
> to
> send messages to a local topic. In fact, it would cause problems if the
> messages went to another router. I would like to be able to define a
> topic
> locally so that it isn't announced to the entire network, but this will
> do.
No problem to define local topics. Just define a hierarchie, starting
with the routername:
router1.mylocaltopic
Subscriptions are propagated throughout the network but messages are only
published locally because you don't have any remote subscriptions.
--
Andreas Mueller, IIT GmbH, Bremen/Germany, http://www.iit.de
SwiftMQ - JMS Enterprise Messaging System, http://www.swiftmq.com
------------------------------------------------------
SwiftMQ developers mailing list * http://www.swiftmq.com
To unsubscribe from this list, send an eMail to
[EMAIL PROTECTED] and write in the body of your message:
UNSUBSCRIBE developers <your-email-address>
Archive: http://www.mail-archive.com/developers@mail.iit.de/
------------------------------------------------------
SwiftMQ developers mailing list * http://www.swiftmq.com
To unsubscribe from this list, send an eMail to
[EMAIL PROTECTED] and write in the body of your message:
UNSUBSCRIBE developers <your-email-address>
Archive: http://www.mail-archive.com/developers@mail.iit.de/
