* UTIL:
- - API-DESIGN: network/connection/client/server: need to communicate
- scheduler's "reason" code for failures to callbacks of the kind
- used by the notify_transmit_ready-family: shutdown and timeout
- may require entirely different actions, and currently we
- cannot tell the difference! [need 4th argument!]
- container_bloomfilter: improve efficiency (see FIXME)
- server: inefficient memmove
- - client: should do exponential back-off (starting at 1ms,
- bounded by 1s) when connection failed (in addition to
- half-time-to-deadline retry at the end)
- Windows: use events instead of pipes to signal select()s [Nils]
- only connect() sockets that are ready (select()) [Nils]
[On W32, we need to select after calling socket before