Quote:
Originally Posted by
ramen_noodle
Praveen: As you yourself noted the utilization of whatever event servicing mechanism you use is going to execute in a thread. Soo I don't think that your question is ingenuous.
My point was that if you service a client with a separate thread you will run out of resources pretty quickly given a sufficiently complex interaction and number of clients.
With asynchronous service and a single thread you do not incur the memory overhead of separate threads and stack space for each.
Frankly Ramen, I never got a chance to use epoll()/kqueue(). I've only been able to use select()/poll() for such event notification machanism, at least in the commercial projects, we've worked on. I also wanted the discussion to be carried further on event notification machanisms so that we get benefited along with many others in the forum and kqueue()/epoll() are good candidates to be discussed. Pl don't take otherwise.
Still may we discuss them further on which Unix/Unix Like platforms support it apart from Linux/BSD (which I've only worked so far)?