On Wed, Nov 12, 2008 at 7:36 AM, Ben Hood <span dir="ltr"><<a href="mailto:0x6e6562@gmail.com">0x6e6562@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Peter,<br>
<div class="Ih2E3d"><br>
On Wed, Nov 12, 2008 at 11:54 AM, Peter Silva <<a href="mailto:Peter.A.Silva@gmail.com">Peter.A.Silva@gmail.com</a>> wrote:<br>
> read about no_ack=false...<br>
> you mean there is no window for acknowledgements?<br>
> you send one, wait for acknowledgment, then send the next?<br>
><br>
> latency will really kill bandwidth on long links. was hoping that one could<br>
> send a large number of messages, and have them acknowledged later (like TCP<br>
> does.)<br>
><br>
> The AMQP spec seems to allow for that, I took it for granted that rabbit did<br>
> that....<br>
<br>
</div>I don't *think* that Dmitriy was implying that there has to be a lock step.<br>
<br>
This is what the protocol says about the basic.ack command:<br>
<br>
"If set to 1, the delivery tag is treated as "up to and including", so<br>
that the client can acknowledge multiple<br>
messages with a single method. If set to zero, the delivery tag refers<br>
to a single message. If the multiple<br>
field is 1, and the delivery tag is zero, tells the server to<br>
acknowledge all outstanding messages. "<br>
<br>
HTH,<font color="#888888"><br>
</font></blockquote><div><br>say you have a 5000 km. link. you can fit oh... several hundred messages in flight (on the fibre between the two points.) It would be better to issue periodic group acknowledgements, but single message acknowledgements would work. I don't get how 'acknowledge all outstanding messages' works. How does the receiver know what is in-flight?<br>
<br> <br></div></div>