You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "james strachan (JIRA)" <ji...@activemq.org> on 2006/03/24 23:22:22 UTC
[jira] Created: (AMQ-658) allow support for 'remote destinations'
allowing clients to send to /consume from a destination on a specified
remote broker
allow support for 'remote destinations' allowing clients to send to /consume from a destination on a specified remote broker
----------------------------------------------------------------------------------------------------------------------------
Key: AMQ-658
URL: http://jira.activemq.org/jira//browse/AMQ-658
Project: ActiveMQ
Type: New Feature
Components: Broker
Reporter: james strachan
It could be the local broker A could talk to a remote broker B; so a client on A talks to destination "MY.QUEUE@A"
Extra brownie points for broker A connected to B connected to C such that A can't see C and sending to MY.QUEUE@C on a client on A would make it to C
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.activemq.org/jira//secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-658) allow support for 'remote destinations'
allowing clients to send to /consume from a destination on a specified
remote broker
Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-658?page=all ]
Hiram Chirino updated AMQ-658:
------------------------------
Fix Version: 4.2
Might be a bit complex to implement.. putting this out for 4.2, perhpas someone will get interested in this issue and bump it up to 4.1?
> allow support for 'remote destinations' allowing clients to send to /consume from a destination on a specified remote broker
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-658
> URL: https://issues.apache.org/activemq/browse/AMQ-658
> Project: ActiveMQ
> Type: New Feature
> Components: Broker
> Reporter: james strachan
> Fix For: 4.2
>
>
> It could be the local broker A could talk to a remote broker B; so a client on A talks to destination "MY.QUEUE@A"
> Extra brownie points for broker A connected to B connected to C such that A can't see C and sending to MY.QUEUE@C on a client on A would make it to C
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira