[usocket-devel] [Patch] ns-try-again-condition is undefined.

Chun Tian (binghe) binghe.lisp at gmail.com
Tue Sep 28 09:30:34 UTC 2010


Thanks all the same.

On Tue, Sep 28, 2010 at 5:27 PM, Stas Boukarev <stassats at gmail.com> wrote:
> "Chun Tian (binghe)" <binghe.lisp at gmail.com> writes:
>
>> Hi, Stas Boukarev
>>
>> You're right. We should always use "ns-try-again-condition" instead of "ns-try-again" as most backends does.
>>
>> Fixed in trunk and earlier branches.
>>
>> P.S. Do you know how to reliably trigger this condition? I want to added "ns-try-again-condition" into our always-broken unit test code, so that all supported platforms could have this condition reported correctly.
> It happened to me when my connection died. I can't think of any software
> method, aside from writing your own nameserver.
>
> --
> With Best Regards, Stas.
>



-- 
Chun Tian (binghe)




More information about the usocket-devel mailing list