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

2010-09-28 Thread Chun Tian (binghe)
Thanks all the same. On Tue, Sep 28, 2010 at 5:27 PM, Stas Boukarev wrote: > "Chun Tian (binghe)" 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. >> >>

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

2010-09-28 Thread Stas Boukarev
"Chun Tian (binghe)" 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-aga

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

2010-09-28 Thread Chun Tian (binghe)
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