Async/Await - OS Concept
There are many question about Async/Await in "dot net"? what really are? what is the issues it handle? is there any dedicated thread/mechanism monitor when a task completes, so notify thread pool to choose thread and continue execution? when to use it? to answer this question let us deep dive a little in some Operating System (OS) concepts and mechanism to handle I/O. What is I/O?:- I/O (input/output), pronounced "eye-oh," describes any operation, program, or device that transfers data to or from a computer. Typical I/O devices are printers, network card, hard disks, keyboards, and mouses. In fact, some devices are basically input-only devices (keyboards and mouses); others are primarily output-only devices (printers); and others provide both input and output of data (hard disks, diskettes, writable CD-ROMs). Programing examples require I/O operations:- - when application query database it get data from hard disk(I/O) - when call api, it call network card(I/O) - w...