Oops, sorry. Something made me believe it was a Github issue notification.
MK
> On 11/9/2015, at 6:25, j...@signafire.com wrote:
>
> I'm confused—I thought this was the mailing list…
> That said, if there's a more appropriate place to ask this question, I'm
> happy to move there.
>
>> On Thurs
I'm confused—I thought this was the mailing list…
That said, if there's a more appropriate place to ask this question, I'm
happy to move there.
On Thursday, September 10, 2015 at 11:20:27 PM UTC-4, Michael Klishin wrote:
>
> Questions belong to the mailing list.
>
> On 11/9/2015, at 6:17, jo...@s
Questions belong to the mailing list.
> On 11/9/2015, at 6:17, j...@signafire.com wrote:
>
> Essentially, it's not clear to me how an application is supposed to recover
> when handling a nack or when langohr.confirm/wait-for-confirms returns false.
> It seems to me that the delivery tag that th
Essentially, it's not clear to me how an application is supposed to recover
when handling a nack or when langohr.confirm/wait-for-confirms returns
false. It seems to me that the delivery tag that the nack handler receives
is only useful if I've been maintaining a map from delivery tags to
messa
