Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <1082308266.1220885758447.JavaMail.jira@brutus>
Date: Mon, 8 Sep 2008 07:55:58 -0700 (PDT)
From: "Gary Tully (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Updated: (AMQ-658) allow support for 'remote destinations'
 allowing clients to send to /consume from a destination on a specified
 remote broker
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/activemq/browse/AMQ-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully updated AMQ-658:
---------------------------

    Fix Version/s: 5.3.0
                       (was: 5.2.0)

> 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
>          Issue Type: New Feature
>          Components: Broker
>            Reporter: James Strachan
>             Fix For: 5.3.0
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.