Open demanuel opened 3 years ago
I've thought about this a couple of times in the last few years and I'm not actually convinced that adding 1.0 support to this module would work very well: the differences in the messaging semantics between the 0.98 that RabbitMQ supports and 1.0 are sufficient that I don't think it would be easy to make a consistent interface (while retaining the existing interface of this module.)
I'd be more inclined to rename this Net::RabbitMQ
(rabbitmq is likely to always support 0.98 as the default protocol because it follows the broker architecture quite closely.) and make a new Net::AMQP that might support both versions but has an interface that reflects the more limited scope of 1.0.
I'd be more inclined to rename this
Net::RabbitMQ
(rabbitmq is likely to always support 0.98 as the default protocol because it follows the broker architecture quite closely.) and make a new Net::AMQP that might support both versions but has an interface that reflects the more limited scope of 1.0.
That would be fine for me. Unfortunately i have to work with apache qpid which only supports AMQP 1.0
Unfortunately i have to work with apache qpid which only supports AMQP 1.0
That was going to be my next question 😃 AFAIK qpid
is the only thing that uses it as its primary (or only,) protocol: all the rest (ActiveMQ, RabbitMQ, IBM MQ et al,) support it as an add-on, though in the case of IBM MQ it would be useful because the native wire protocol isn't documented and the libraries, er, show their early '70s heritage.
Hi!
Any chance of supporting AMQP 1.0 ? The AMQP working group released the 1.0 specification in the final quarter of 2011.
Best regards, David Santiago