aderouineau wrote:But the value of the limit can be changed at compile time, if I'm correct; and although I plan on making it multi-platform, I'll advise not to use it on windows (after all, who wants to trust windows for highly scalable apps :p).
I don't know if it would be wise to change that limit though... What do you think?
I don't think that is a problem, although according to C10K
page some std libraries have it compiled in:
Unfortunately, select() is limited to FD_SETSIZE handles. This limit is compiled in to the standard library and user programs. (Some versions of the C library let you raise this limit at user app compile time.)
aderouineau wrote:Is EPOLL used for polling? If I remember correctly, there's a project (not a framework) that can use two different polling libraries.
No - poll(2) is used. C10K
page is the best source on async IO I know of.
aderouineau wrote:Since polling is only available in trunk, I guess I can just use Reactor with normal select during development, and hopefully polling will be in stable when I'll be done with the app (probably some time around september). Will polling be in stable then?
I would love it to be, but I can not promise. Few months ago, someone offered to sponsor async IO development
, but that was a solitary offer and there was not much interest from other parties to contribute. We love to code, but life has its demands, so without something like that, it is hard to make firm promises.
aderouineau wrote:I'm also wondering about the real performance difference between poll and select...
page for answer to that.