Andrius can certainly clarify, but I took the statement, "We'd like to support a scenario where some of the nodes run a non-Artemis AMQP broker, and it's still possible to interoperate," to mean that the bridge's protocol should be AMQP so it will be compatible with other brokers.
Andrius, can you comment on this? Justin On Thu, Jul 27, 2017 at 3:05 PM, Clebert Suconic <clebert.suco...@gmail.com> wrote: > form what I understood.. he wanted AMQP because of the core-bridge > wouldn't support the AMQP format. but if you can actually transfer an > AMQP message between broker.. it wouldn't matter what's being used... > unless they want to be that specific. > > On Thu, Jul 27, 2017 at 3:41 PM, Justin Bertram <jbert...@redhat.com> > wrote: > > In that case, your fix (while needed) wouldn't help in this use-case > since > > they're trying to connect between nodes via AMQP. > > > > I think either Qpid Dispatch Router or a Camel have the most promise at > > this point. > > > > > > Justin > > > > On Thu, Jul 27, 2017 at 2:36 PM, Clebert Suconic < > clebert.suco...@gmail.com> > > wrote: > > > >> If an AMQP message is going through the bridge. I would embed the wrap > the > >> message Before send. Unwrap at receiving. > >> > >> That is the protocol is still core. But it would wrap non core messages > >> instead of converting it. > >> > >> On Thu, Jul 27, 2017 at 2:44 PM Justin Bertram <jbert...@redhat.com> > >> wrote: > >> > >> > Clebert, are you changing the core bridge to support Artemis' internal > >> AMQP > >> > message representation or are you implementing a bridge that uses the > >> AMQP > >> > protocol? > >> > > >> > > >> > Justin > >> > > >> > On Thu, Jul 27, 2017 at 1:19 PM, Clebert Suconic < > >> > clebert.suco...@gmail.com> > >> > wrote: > >> > > >> > > On Thu, Jul 27, 2017 at 2:07 PM Justin Bertram <jbert...@redhat.com > > > >> > > wrote: > >> > > > >> > > > Thanks for the explanation. That seems like it would be a good > >> > use-case > >> > > > for Camel bridging between two JMS providers. > >> > > > > >> > > > >> > > Regardless I will have to fix the core bridge to load balance amqp > as > >> > well. > >> > > > >> > > > >> > > > >> > > > > >> > > > Justin > >> > > > > >> > > > On Thu, Jul 27, 2017 at 12:54 PM, Clebert Suconic < > >> > > > clebert.suco...@gmail.com > >> > > > > wrote: > >> > > > > >> > > > > Check back in a week. I'm working on it. > >> > > > > > >> > > > > On Thu, Jul 27, 2017 at 1:34 PM adagys <andrius.da...@r3.com> > >> wrote: > >> > > > > > >> > > > > > Thanks, I'll have a look at Dispatch. > >> > > > > > > >> > > > > > The use-case is a distributed ledger platform, where we have a > >> > > > > peer-to-peer > >> > > > > > network of nodes operated by different parties. Each node > runs an > >> > > > Artemis > >> > > > > > broker, and maintains queues for messages to other nodes, > which > >> get > >> > > > > > forwarded using core bridges. We'd like to support a scenario > >> where > >> > > > some > >> > > > > of > >> > > > > > the nodes run a non-Artemis AMQP broker, and it's still > possible > >> to > >> > > > > > interoperate (the non-Artemis broker might also require some > >> > > additional > >> > > > > > bridging support). > >> > > > > > > >> > > > > > For more context: > >> > > > > > > >> > https://docs.corda.net/key-concepts-ecosystem.html#network-structure > >> > > > > > <https://docs.corda.net/key-concepts-ecosystem.html# > >> > > network-structure> > >> > > > > > > >> > > > > > > >> > > > > > > >> > > > > > -- > >> > > > > > View this message in context: > >> > > > > > http://activemq.2283324.n4.nabble.com/Artemis-AMQP- > >> > > > > bridges-tp4728934p4728978.html > >> > > > > > Sent from the ActiveMQ - User mailing list archive at > Nabble.com. > >> > > > > > > >> > > > > -- > >> > > > > Clebert Suconic > >> > > > > > >> > > > > >> > > -- > >> > > Clebert Suconic > >> > > > >> > > >> -- > >> Clebert Suconic > >> > > > > -- > Clebert Suconic >
