Agreed - yes we should add the ability to have 'remote destinations' such that we publish messages directly to a remote broker, rather than the current broker you are connected on.
I've raised a JIRA for this http://jira.activemq.org/jira/browse/AMQ-658 James On 3/24/06, d j <[EMAIL PROTECTED]> wrote: > > Hi James, > Yes. Whether is single broker of clustered broker is not important. Same > queue name can be used at any broker, but when a publisher wants to publish > to a queue, it wants to publish on the queue at specific broker, which is > identified by network domain or realm. Let's say a myQueue can be > myQueue.brokerC. A message sinding at brokerA to myQueue will be routed to > myQueue.brokerC based on domain name or realm. It's something like > multi-domain routing. And it might make the deployment much easier when > deploying multiple brokers at different networks. I don't know much about > how the JMS broker works. What i said might be wrong. > Thanks. > -- > View this message in context: > http://www.nabble.com/jms-routing-t1333152.html#a3577310 > Sent from the ActiveMQ - User forum at Nabble.com. > > -- James ------- http://radio.weblogs.com/0112098/
