Re: Syslets, Threadlets, generic AIO support, v6

["Albert Cahalan" <acahalan@gmail.com>]

Ingo Molnar writes:

> looking over the list of our new generic APIs (see further below) i
> think there are three important things that are needed for an API to
> become widely used:
>
>  1) it should solve a real problem (ha ;-), it should be intuitive to
>     humans and it should fit into existing things naturally.
>
>  2) it should be ubiquitous. (if it's about IO it should cover block IO,
>     network IO, timers, signals and everything) Even if it might look
>     silly in some of the cases, having complete, utter, no compromises,
>     100% coverage for everything massively helps the uptake of an API,
>     because it allows the user-space coder to pick just one paradigm
>     that is closest to his application and stick to it and only to it.
>
>  3) it should be end-to-end supported by glibc.

4) At least slightly portable.

Anything supported by any similar OS is already ahead, even if it
isn't the perfect API of our dreams. This means kqueue and doors.

If it's not on any BSD or UNIX, then most app developers won't
touch it. Worse yet, it won't appear in programming books, so even
the Linux-only app programmers won't know about it.

Running ideas by the FreeBSD and OpenSolaris developers wouldn't
be a bad idea. Agreement leads to standardization, which leads to
interfaces getting used.

BTW, wrapper libraries that bury the new API under a layer of
gunk are not helpful. One might as well just use the old API.