[rabbitmq-discuss] Unofficial guide to AMQP 1.0 PR3

[Jason Pellerin]

On Wednesday 05 May 2010 18:38:18 Michael Bridgen wrote:

> Flow control acts like a more fine-grained channel.flow for publishers,
> and like basic.qos for consumers; in each case, the receiving side
> issues *credit*, which the sending side uses up by transferring
> messages.  To do something like a basic.get, a consumer issues a single
> unit of *credit*, and waits for the single message to come in.

I hope I'm missing something, but this description jumped out at me as looking
like AMQP 1.0 is going to include one of (IMO) 0-10's biggest mistakes.

As someone using messaging mainly in web applications, basic.get is the best
thing in amqp. When response time matters, having a single command that polls
for a message and returns immediately if one isn't present is incredibly
useful. Replacing that with 2+ commands and replacing polling with waiting --
ouch.

JP

CONFIDENTIALITY NOTE
The document(s) accompanying this e-mail transmission, if any, and the e-mail transmittal message containing information from Leapfrog Online Customer Acquisition, LLC is confidential or privileged. The information is intended to be for the use of the individual(s) or entity(ies) named on this e-mail transmission message. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this e-mail is prohibited. If you have received this e-mail in error, please immediately delete this e-mail and notify us by telephone of the error.