Lines Matching +full:high +full:- +full:performance

1 Windows-related issues
16 structure which embeds a fixed-length array of socket handles. This is necessary
21 Neither select() nor poll() are, of course, high performance polling options.
22 Windows does not provide anything like epoll or kqueue. For high performance
27 is that IOCPs are a higher-level interface; it is easy to build an IOCP-like
29 polling-like interface on top of IOCPs.
34 just to write a poll-based implementation of an I/O reactor and an IOCP-based
41 actually more similar to a high-level asynchronous I/O library such as libuv or
46 - ddd-01-conn-blocking: Blocking example, use of IOCP is not applicable.
48 - ddd-02-conn-nonblocking: Socket is managed by OpenSSL, and IOCP is not
51 - ddd-03-fd-blocking: Blocking example, use of IOCP is not applicable.
53 - ddd-04-fd-nonblocking: libssl is passed an FD with BIO_set_fd.
55   BIO_s_sock doesn't appear to support overlapped (that is, IOCP-based) I/O
64 - ddd-05-mem-nonblocking: Since the application is in full control of passing
70 - ddd-06-mem-uv: This demo uses a memory BIO and libuv. Since libuv supports
71   IOCP, it proves that a memory BIO can be used to support IOCP-based usage.
75 So ddd-05 and ddd-06 essentially demonstrate this use case, especially ddd-06 as