Re:Interview with Ryan Dahl, Creator of Node.js
by int_19h on Friday September 01, 2017 @06:25AM
(#15147321)
This is a bug in the library. The correct way to do these "async but not really" wrappers is to call the synchronous implementation in a separate thread pool worker thread, and wrap that into a task (as Task.Run does). This is hardly optimal perf-wise, but it is truly asynchronous wrt to the caller. If I remember correctly, it's what Stream does for its default implementations of async methods.
[ Parent
| on HN ]
There are no comments on this comment yet.