What does it mean to be “truly” asynchronous?
Reading the Proactor pattern paper, specifically this part:
What does it mean to be “truly” asynchronous?
Reading the Proactor pattern paper, specifically this part:
TCP connection-oriented synchronous data write
thinking about the design of an IoT project where the devices don’t have a standard application layer but rather a thin custom application layer utilizing TCP sockets. What I mean by this is that the device wakes up every 15 minutes or so opens a socket on the server and sends data in, waits for any incoming data and then goes back to sleep/powers off.
Asynchronous HTTP request pattern
Here is the pattern that I thought about for a resource accepting a single asynchronous HTTP request at a time (i.e. a request which has not yet been fulfilled when the response is sent):