14 Dec
2005
14 Dec
'05
4:13 p.m.
Arkadiy Vertleyb wrote:
Let me disagree with this. There are cases when having multiple threads, each working in a synchronous way, is a better approach. First, it's much more intuitive, and easier to debug. Second, sometimes it's the only way to achieve you goal, such as whan you can't (or don't want to) rewrite your processing algorithm in asynchronous way.
And when such a case arrives, it would be nice to have a clean socket class, without build-in asynchronisity.
Even if this is the case, is it the responsibility of a library that offers Asynchronous I/O as a primary focus to supply a clean socket class that has nothing to do with async I/O?