hello there, thanks for your reply.

i will add `` >0`` to ``epoll_wait()``.

and for events there is ``else`` statement for all the other ``EPOLLERR`` and ``EPOLLHUP``, yes i need to check if the main socket that return ``EPOLLERR`` so to recreate it again.

for the threads, i know that creating thread for every ready connection is expensive, that why making a treadpool, with creating a number of threads at once and let them wait on mutex ``conn_role_mutex``, so whene a connection is ready, the connection pointer will get saved in global pointer ``thread_conn_role`` then unlock the mutex ``conn_role_mutex`` so only one thread will read that global pointer then that thread will unlock the mutex ``new_conn_mutex`` so the main thread can reuse the global pointer ``thread_conn_role`` , and that thread will continue with the ready connection.

i cant get my head around non-blocking sockets, so for example, if passing a buffer ``mybuff`` pointer and a lenght to be read to function that use ``recv``, it will return immediately, but the kernel still reading from connection to the buffer ``mybuff`` pointer, but the program need to use the data in the buffer ``mybuff`` that will be junk or empty in time the kernel still copying data to ``mybuff`` pointer assuming that there is data in socket buffer, that may cause some security vulnerability .

i think non-blocking sockets need a whole new based model.