ERights Home elib / concurrency 
Back to: The Four Layers of When 1st child: EIO Design Goals On to: The Joule MultiChannel

EIO:
E's Non-blocking I/O Library


Design Goals What requirements and preferences shaped EIO's design?
API The javadoc-umentation of the EIO package.
Obtaining elements from an InStream Further documentation on the InStream API.

There's a live discussion of the design of this API on the E Language Wiki root page.

Acknowledgements

This EIO design has been thrown out and redone several times. Were it not for the many insightful contributions and criticisms I received, I have no doubt I would have stuck with one of my earlier attempts. The current EIO design is mostly by E-Dean Tribble and Mark Miller, with contributions and influences by at least Chip Morningstar, Norm Hardy, Danfuzz Bornstein, Zooko, and Constantine Plotnikov. (If I forgot to include you, please let me know.)

 
Unless stated otherwise, all text on this page which is either unattributed or by Mark S. Miller is hereby placed in the public domain.
ERights Home elib / concurrency 
Back to: The Four Layers of When 1st child: EIO Design Goals On to: The Joule MultiChannel
Download    FAQ    API    Mail Archive    Donate

report bug (including invalid html)

Golden Key Campaign Blue Ribbon Campaign