On Mon, 20 Jan 2014 10:32:01 GMT, Sönke Ludwig wrote:

I've just taken a quick look, but if ENetSocket is an alias for int or SOCKET or if it is possible to somehow get the socket number, you can use the new createSocketFileDescriptorEvent to avoid polling (see this thread). In that case everything should run reasonably efficient (not sure how ENet handles the zero timeout, but that shouldn't be an issue because you'd basically never run into it).

However, I've done some research on libevent and now have a much better perspective on what's going on. I didn't know that UDPConnection's recv registered an event and was blocking. But now it makes sense. Unfortunately, this makes the ENet library less than useful in this scenario. I think I'll just cook something of my own up and use TCP in the meantime.

Thanks,
Kelet