On 7 March 2012 15:00, Matt Pietrek <span dir="ltr"><<a href="mailto:mpietrek@skytap.com">mpietrek@skytap.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="font-size:14px;font-family:Calibri,sans-serif;word-wrap:break-word"><div>My current understanding is "no".</div></div></blockquote><div><br>Correct. The scope of the delivery-tag field in Basic.Deliver and Basic.Ack is the channel that the Basic.Deliver appeared on. Once that channel's closed (either directly, or indirectly through a connection close or TCP abort), the delivery-tag will no longer be understood by the remote peer: its scope has ended.<br>
<br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="font-size:14px;font-family:Calibri,sans-serif;word-wrap:break-word"><div>So the question is, after the reconnect, should we even attempt to acknowledge messages read from the original connection?</div>
</div></blockquote><div><br>No.<br><br>(Questions like this highlight some of the reasons why "exactly-once" delivery isn't really a meaningful feature for messaging middleware to provide :-) )<br><br>Regards,<br>
� Tony<br><br></div></div>-- <br>Tony Garnock-Jones<br><a href="mailto:tonygarnockjones@gmail.com" target="_blank">tonygarnockjones@gmail.com</a><br><a href="http://homepages.kcbbs.gen.nz/tonyg/" target="_blank">http://homepages.kcbbs.gen.nz/tonyg/</a><br>