4 Aug
2005
4 Aug
'05
2:59 p.m.
Edward Diener wrote:
Any networking library which does not have non-blocking asynchronous support for network I/O is, IMO, doomed to general non-use.
For what it's worth, I completely agree. Scott Woods wrote:
if you ultimately want to provide both a blocking and non-blocking API it is less difficult to imagine a non-blocking API over a blocking API than the other way around.
I take it you meant the opposite? A non-blocking API can be trivially wrapped to block, but the other way round doesn't work too well.