Better documentation of asynchronous I/O implementation per OS about dotnet-api-docs HOT 7 OPEN

Perhaps a detailed blog post about our Sockets model/implementation would be useful.

from dotnet-api-docs.

Thanks for the great suggestion. I agree we should document this. For now, here's a (very quick) summary:

1. On Windows, Sockets uses I/O Completion Ports for async operations, via the CoreCLR thread pool.
2. On Linux, we use non-blocking sockets, and a single thread monitoring for status via epoll. User callbacks are posted to the CoreCLR thread pool once the I/O operation is complete.
3. On OSX, it works just like Linux, except we're using kqueue instead of epoll.

from dotnet-api-docs.

@karelz We think this should be re-routed to perhaps System.IO or other documentation team. Can you pls re-route.

from dotnet-api-docs.

cc: @geoffkizer

from dotnet-api-docs.

@davidsh just change the area label and it will take care of itself :)

from dotnet-api-docs.

And if you want to be really nice, you can tag area owners -- cc @JeremyKuhne @ianhays.

from dotnet-api-docs.

This doesn't sound like a System.IO issue to me. Sounds like it's squarely about Sockets. Am I missing something?

from dotnet-api-docs.