Skip Menu |

This queue is for tickets about the AnyEvent-RabbitMQ CPAN distribution.

Report information
The Basics
Id: 71099
Status: resolved
Priority: 0/
Queue: AnyEvent-RabbitMQ

People
Owner: Nobody in particular
Requestors: alex [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: (no value)
Fixed in: (no value)



Subject: documentation for net::rabbitfoot vs anyevent::rabbitmq
It is not at all apparent whether one or the other of these modules is deprecated. The documentation is substantially similar, but the underlying code is different. Further, the date on each seems to imply that anyevent::rabbitmq supersedes net::rabbitfoot, but the fact that net::rabbitfoot depends upon anyevent::rabbitmq disputes this. The code (that is, comments in the code) for neither clarifies this issue. I realize docpatches are a pain, but it would be very nice if the relationship between the two could be explained more clearly in the documentation for either (or each). I have added this report to anyevent::rabbitmq because Ikuta owns both, and the latter seems to be the newer. -- alex avriette alex@cpan.org
Net::RabbitFoot is a blocking client (i.e. it waits for the server for any requests you send it), whereas AnyEvent::RabbitMQ is asynchronous. I have tried to clarify this in the docs: https://github.com/bobtfish/AnyEvent-RabbitMQ/commit/dd25a0b3a300f35fe2f025775b406f562ff49833 please let me know if that isn't clear (and suggest some text to make it clearer?). Thanks for the bug report!