Joshua Kramer wrote:
and the existing APIs, which are centered around the AMQP 0-10 model,
with exchanges, bindings, queues, etc. To use the new API, a
programmer need not think of exchanges at all, but anyone who uses
the management tools sees
Nice timing. :) I have a Linux Journal artic
and the existing APIs, which are centered around the AMQP 0-10 model, with
exchanges, bindings, queues, etc. To use the new API, a programmer need not
think of exchanges at all, but anyone who uses the management tools sees
Nice timing. :) I have a Linux Journal article going to press today
The new messaging client API is designed to hide the details of specific
AMQP versions. This causes a certain impedance mismatch with the
maangement tools and the existing APIs, which are centered around the
AMQP 0-10 model, with exchanges, bindings, queues, etc. To use the new
API, a programm
