Re: [Libevent-users] thread-safety bug report with patch

2008-02-26 Thread Nick Mathewson
On Tue, Feb 26, 2008 at 10:12:08AM -0800, Tani Hosokawa wrote: These are four broken functions that didn't make it into the latest release -- I noticed that one of them is even marked as not being thread-safe. Thanks! I've checked your patch into trunk and into the 1.4 branch.

Re: [Libevent-users] performance patch

2008-02-26 Thread William Ahern
On Wed, Feb 27, 2008 at 02:54:41AM +0300, Vsevolod Stakhov wrote: Tani Hosokawa ?: snip significant amount of processing to do per request. The reason I put 1024 in there is all implementations that I know of silently truncate the backlog parameter to the system's maximum. The reason I

Re: [Libevent-users] performance patch

2008-02-26 Thread Niels Provos
On Tue, Feb 26, 2008 at 12:41 PM, Tani Hosokawa [EMAIL PROTECTED] wrote: Under high load, unless you build a dedicated acceptor thread you will find that only allowing a listen backlog of 10 connections will cause lots of attempted connections to simply be dropped if you have any

[Libevent-users] dns server availability check / google.com

2008-02-26 Thread Florian Lohoff
Hi, while looking into an async dns solution i found the code to recheck dns servers in libevent. I dont think checking for google.com is a very good choice. In the past even ccTLDs have disappeared or start to disappear (.su, .dd, .yu) despite companys renaming, disappearing or having hicups.