<div dir="ltr"><span style="font-family:arial,sans-serif;font-size:13px">Hi,</span><br style="font-family:arial,sans-serif;font-size:13px"><div class="gmail_quote" style="font-family:arial,sans-serif;font-size:13px"><div dir="ltr">
<div><br></div><div>(I originally posted this to rabbitmq-discuss@googlegroups but it apperas not to have replicated to the 'proper' list so apologies for any duplication of this message)</div><div><div class="adm">
<div id="q_142515f0fc069d58_1" class="h4"><div class=""></div></div></div><div class="im"><div><br></div><div>Would it be possible to write a rabbitmq plugin to intercept delivery to a queue to add/increment a delivery counter header value? I can't see an appropriate behaviour to implement in the source but my understanding of the rabbitmq code base isn't good enough to properly see what can and can't be done. </div>
<div><br></div><div>After spending a fair bit of time thinking about a generic poison message strategy it feels a broker based counter (rather than the existing redelivered flag) would be the most appropriate for the kind of system we are currently writing (integrations / dirty data) and if we could at least get some kind of delivery counter working (100% would not be required) we could handle rejection strategies better at the consumer.</div>
<div><br></div><div>I know there is a planned feature for this (basic / deliver / 01) but I checked with Alvaro who has confirmed it isn't a priority at this time so we could do with some kind of half-way house in the meantime.</div>
<div><br></div><div>I'd appreciate any suggestions / advice you may have on this topic.</div><div><br></div><div>Many thanks</div><font color="#888888">Karl</font></div></div></div></div><div><br></div>-- <br><b>Karl Nilsson</b><div>
twitter: @kjnilsson</div><div><br></div>
</div>