io-completion-ports

I recently was made aware of this thing called IOCP on windows and i began searching for more information on it but i couldn't find anything up to date (most of the examples were on codeproject almost 5 years old) and not too many guides or tutorials. Can anyone recommend any up to date resources about it in the form of online tutorials or example projects (that you wrote and can share or other open source projects) or even a book about it because if it's as good as it sounds i plan to use it extensively so i will invest in it. Thank You. IOCP is a feature that has been in Windows since the

Based on numerous books and blogs including this excellent one here , it is clear that when one writes a dll library exposing helper async methods i.e. the wrapper methods, it is generally considered a best practice to internally complete the I/O task of actual async methods on a threadpool thread like so (pseudo code shown below for brevity and I'm using HttpClient as an example) public Async Task<HttpResponseMessage> MyMethodAsync(..) { ... var httpClient = new HttpClient(..); var response = await httpClient.PostAsJsonAsync(..).ConfigureAwait(false); ... return response; } The key here is

I'm wondering which approach is faster and why ? While writing a Win32 server I have read a lot about the Completion Ports and the Overlapped I/O, but I have not read anything to suggest which set of API's yields the best results in the server. Should I use completion routines, or should I use the WaitForMultipleObjects API and why ? You suggest two methods of doing overlapped I/O and ignore the third (or I'm misunderstanding your question). When you issue an overlapped operation, a WSARecv() for example, you can specify an OVERLAPPED structure which contains an event and you can wait for that