In article <abf38541e17a0ddacbed5fc06cfd3066@cs.indiana.edu>, Douglas Gregor <doug.gregor@gmail.com> wrote:
On Apr 12, 2005, at 8:54 PM, Boris wrote:
I updated http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl? BoostNet to document why what decisions were made.
We have until now: * The network library should support four I/O models which are known to many programmers as blocking, non-blocking, multiplexing and asynchronous.
I think the scope of this library is insane. We don't need to solve every single network I/O problem with one huge networking library. Having a solid socket library that handles only blocking with be a _huge_ improvement . Start small and don't be afraid to say "No! That's for the next version."
I agree. There are several libraries that I think have suffered from scope creep and a v1 of smaller scope would have been very useful to a substantial number of people. (Logging library comes to mind.) meeroh