[ http://jira.jboss.com/jira/browse/JBMESSAGING-264?page=comments#action_12... ] Colin Stefani commented on JBMESSAGING-264: ------------------------------------------- This is a feature that is crucial to my operations as a JMS user and it one thing keeping me off of many JMS implementations. As a result we use Tibco EMS which has a feature called "bridging" (aka message bridge as noted by Tim Fox). This is a VERY high performance internal replicator of messages between topics and/or queues or vice versa. One important element of this is to be able to apply a selector or filter on the bridge (much like one might do on a client connection to filter messages). This would allow the admin or developer creating the bridge to narrowly select the messages with the matching filter properties to deliver messages to a destination w/o having to write an elaborate external bridge piece of software. Speed is critical in this as it should be considered almost like the producer of the message is delivering the message to both locations. Tibco EMS seems to be able to produce an "OnMessage" event to clients in both the original target queue or topic and the bridged queue or topic in nearly the same timeframe. Don't know if this will help when you get to this feature, but I've been keeping my eye on it from afar and if had my $0.02, I'd say worry less about the bridges to external destinations but instead focus on a feature for internal bridges first. For external or remote destination message delivery, I would treat those as a clients and create a routing mechanism that's not as "real-time" as a bridge would be. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira