Add support for polling HANDLEs

[sdroege]

HANDLEs are used for waitable timers, named pipes, various synchronization primitives, event objects and various other "pollable" things on Windows. Would be nice to be able to poll them in addition to SOCKET.

[piscisaureus]

Would be nice, but (at least in older windows versions) there's no reasonable way to do it.

I noticed that windows 10 now has the 'NtAssociateWaitCompletionPacket' syscall; if that does what the name suggests that might be an option to look into.

I currently have very little time to further develop wepoll, so if you want to take a stab at it I'd suggest you fork it and/or send a PR.

[sdroege]

With WaitForMultipleObjects() SOCKET and HANDLE work the same way, but I guess you're not using that then :)

[smumriak]

With WaitForMultipleObjects() SOCKET and HANDLE work the same way, but I guess you're not using that then :)

necroposting, but might be useful for time travelers: alll WaitForObject(s) APIs in win32 (i.e. winapi) have a limitation of maximum 64 handles to be waited on. that does not scale, not even close to what this library aims to support

[notgull]

I noticed that windows 10 now has the 'NtAssociateWaitCompletionPacket' syscall; if that does what the name suggests that might be an option to look into.

Interesting; how would this work? Do you just call NtAssociateWaitCompletionPacket with the target handle (a file?) and the IOCP and then, once the handle is "ready", it shows up in the IOCP?