[Mono-devel-list] PATCH: reworked async IO for Socket

[James Mansion]

>Epool, kqueue and async IO all share the same problem: they are barely
>portable.

They don't really have to be - there are plenty of
examples of how to wrap them up to create a virtual layer
that *is* portable.  You only need 'one of' these
technologies on any given platform, and configure can
take care of the rest.

Given the effectiveness of P/Invoke and dynamic loading,
the portability layer could be in C#.

AIO I would ignore, *that* suffers from the IMO worse
fate of portable APIs and generally half-baked
implementations that are passable on a small number
of disk devices and rubbish on large numbers of
sockets.

Sometimes, Microsoft do things right.

James