Note: None of this is implemented or really designed. Thus, this text is exploratory in nature, for now.

I/O encompasses any processing activity that extends beyond the boundaries of CPU/memory computation, including user input and presentation, file or network requests, timers, etc. From the perspective of the CPU, I/O activity can often take a long, indeterminate amount of time, which presents a complicating challenge to efficiently scheduling concurrent work.

In essence, we want to satisfy these essential requirements:

There are several architectural approaches to satisfy these requirements:

Currently, the projected design for Cone is leaning towards an Actor-based approach for handling asynchronous I/O, sequential workflows, and cancellability.