Lines Matching full:windows

1 Windows-related issues
4 Supporting Windows introduces some complications due to some "fun" peculiarities
5 of Windows socket API.
7 In general, Windows does not provide a poll(2) system call. WSAPoll(2) was introduced
10 finally fixed this bug in a build of Windows 10. So WSAPoll(2) is a viable
11 method, but only on fairly new versions of Windows.
13 Traditionally, polling has been done on windows using select(). However, this
15 platforms select() accepts a bitmask of FDs, on Windows select() accepts a
17 because sockets are NT kernel handles on Windows and thus are not allocated
18 contiguously like FDs. As such, Windows select() is actually very similar to
19 POSIX poll(), making select() a viable option for polling on Windows.
22 Windows does not provide anything like epoll or kqueue. For high performance
23 network I/O, you are expected to use a Windows API called I/O Completion Ports
44 Evaluation of the existing demos and their applicability to Windows IOCP:
76 it uses IOCP internally on Windows.