Re: [libmicrohttpd] Thread Pooling

[phoenix]

Threadpool... epoll... WANT!


>> I'd say let's keep it simple: add new connections to the thread with
>>the
>> fewest number of active connections.  Given that most will be short-lived
>> and most connections will have similar characteristics, I think this should
>> result in at least decent load balancing. Moving connections between
>> threads would require locking which would then possibly be a bigger
>> bottleneck then what would be caused by a possible imbalance. Asking the
>> application for help would really complicate the API so that's really not a
>> good idea in my book.
>
>Sounds good to me.  I'll try to get the basic thread pooling done as soon as I 
>can, then look at epoll/select within the threads after that.
>
>-- 
>Richard Alimi
>Department of Computer Science
>Yale University