On 04/15/2014 01:53 PM, Rob Godfrey wrote:
From an AMQP 1.0 perspective, the broker really shouldn't need telling.
The question is really how to determine if/when the broker should flush
any writes to disk. Durable messages will only be considered settled
when the broker can be sure the enqu
>From an AMQP 1.0 perspective, the broker really shouldn't need telling.
The intention was that a container may decide to batch information it has
on hand, but it should always be "prompt" in informing its peers of
disposition changes. So its valid to wait until you've finished process a
batch of
Hello,
I have spotted a performance-impacting lack in AMQP 1.0 implementation of
session.sync() in C++ client. On AMQP 0-10, the method sends execution.sync
frame to the broker, asking for prompt delivery status to be sent. But 1.0
client does not invoke any such command. For performance impact,
