On Mon, Nov 13, 2006 at 12:44:05PM -0800, Donn Cave wrote:
Threads, maybe? Is blocking I/O seriously incompatible with the GHC
threading model (or one of the models)?
The problem is that a blocking IO call would block all threads. We could
execute all such calls in their own OS thread, but
[reposted with improved subject]
I notice that the Socket returned by ghc Network.Socket (socket) has
been set non-blocking. (Noticed empirically, not from documentation.)
The Network.Socket functions that use it, e.g., recv, are ready for
that, of course, but as a general rule, external
