Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
MIME-Version: 1.0
In-Reply-To: <1501082187962-4728934.post@n4.nabble.com>
References: <1501082187962-4728934.post@n4.nabble.com>
From: Justin Bertram <jbertram@redhat.com>
Date: Wed, 26 Jul 2017 14:54:08 -0500
Message-ID: <CAF+kE=TCgHAiM+1xLOMES9ekkM3eEj754v+gbnufk_RVnzzjaw@mail.gmail.com>
Subject: Re: Artemis: AMQP bridges
To: users@activemq.apache.org
Content-Type: multipart/alternative; boundary="001a1137baaea7b56105553dcf4a"
archived-at: Wed, 26 Jul 2017 19:54:21 -0000

--001a1137baaea7b56105553dcf4a
Content-Type: text/plain; charset="UTF-8"

I'm curious about the use-case here.  Can you elaborate on this a bit?

As Clebert mentioned, Qpid Dispatch Router may fit your needs.  For certain
use cases it can be quite powerful.


Justin

On Wed, Jul 26, 2017 at 10:16 AM, adagys <andrius.dagys@r3.com> wrote:

> In our setup we have multiple independent Artemis brokers, linked together
> by
> core bridges to form a peer-to-peer network. We'd like to ensure that the
> wire-level protocol used is always AMQP (1.0), but the core bridges seem to
> only support core (which makes sense) and perform message conversion.
>
> How feasible would it be to create a custom AMQP bridge implementation and
> what sort of issues we'd likely hit? Could you recommend any other
> approaches here?
>
> Thanks
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/Artemis-AMQP-bridges-tp4728934.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

--001a1137baaea7b56105553dcf4a--