Hi all,
I've been watching this thread with interest (partially in the hope of
an example as well!) An example of atomic update of direct bindings
does sound very interesting. Is it possible to get at this from Java?
(Pure JMS not a requirement).
Cheers,
Andrew
Background: we're examining ways to get reliable app-level node
failover without losing messages. Best thing we've got so far is
durable JMS topic subscriptions, and a backup app node taking over a
client id if the primary node fails. But this atomic-swap of direct
bindings could be useful alternative/addition. We're looking at a java
based client, with a c++ broker.
On 22 Jan 2009, at 15:51, Carl Trieloff wrote:
Adam,
there is now also an option to atomically update a direct binding.
This means that you can
move where the messages are being routed without fear.
This would also be a very simple way to do this use case.
if you want to try that I can give it a try I send an example on how
to
Carl.
Adam Chase wrote:
Any luck on this headers exchange wiki page? I'd be content with
just
a basic outline.
Thanks,
Adam
On Thu, Jan 8, 2009 at 3:24 PM, Robert Greig <robert.j.gr...@gmail.com
> wrote:
2009/1/7 Carl Trieloff <cctriel...@redhat.com>:
We do support the headers exchange, so that can be used. Maybe
the best
thing is to
doc the pattern on a wiki page using headers exchange for Adam.
Are you able
to do that?
Yes, I'll take a look at writing that up over the next few days. I
think it will work, although it is more complex than the selector
case.
RG
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscr...@qpid.apache.org
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscr...@qpid.apache.org
