Comment by cryptonector
5 days ago
From an abstract API perspective it doesn't matter: it's just fire-and-forget where you call a function that will start some I/O and you associate some sort of event completion notice. The details matter only regarding performance.
For this to work, your API has to be an async I/O API not an event listening API. It can't be "wait for readable" - it has to be "do a read and wait for it"
No, it's "launch a read and elsewhere get a completion event".
"do a read and wait for it" is synchronous I/O.