[Libevent-users] How does libevent deal with more events than a particular syscall can handle?

2006-11-18 Thread Roger Clark
For instance, the maximum number of fds usable by select() on Win32 (or other platforms) is low compared to the number of potential connections needed by a high-throughput HTTP server. Does libevent call the dispatcher multiple times on different sets of events? How does the design of the

Re: [Libevent-users] How does libevent deal with more events than a particular syscall can handle?

2006-11-18 Thread Steven Grimm
It avoids using select() unless there's absolutely no other choice, in part because of the artificial limits of select() but mostly because select() is inefficient for large numbers of monitored file descriptors. Most of the point of libevent is that it's a generic wrapper around OS-specific

Re: [Libevent-users] How does libevent deal with more events than a particular syscall can handle?

2006-11-18 Thread Roger Clark
Has there ever been any mention of using IOCP or something on Windows? The Win32 implementation currently uses select() and still imposes the limit, which was mainly why I was asking. Furthermore, does there appear to be any activity on this project regarding Windows at all? -- Roger Clark

Re: [Libevent-users] How does libevent deal with more events than a particular syscall can handle?

2006-11-18 Thread Nick Mathewson
On Sat, Nov 18, 2006 at 05:53:24PM -0500, Roger Clark wrote: For instance, the maximum number of fds usable by select() on Win32 (or other platforms) is low compared to the number of potential connections needed by a high-throughput HTTP server. Check out the C code; it's all there. :) On