"Christopher Kohlhoff" <chris@kohlhoff.com> wrote in message news:20050818142216.76498.qmail@web32610.mail.mud.yahoo.com...
As discussed in the "surveying async network io libraries" thread, I'd like to turn asio (asio.sourceforge.net) into a proposal for a boost networking library.
Sound great :-) I skimmed the docs and your tutorial seems to be very nice so far. (the links are good) I havn't followed the discussion, so this is just my random input. 1. I hate cryptic short names like dgram_socket. recv why not write datagram and receive? (the other short names seems ok and quite standard) Looking at the Daytime1 example, I wounder why 2. asio::ipv4::host host; host_resolver.get_host_by_name(host, argv[1]); is not written asio::ipv4::host host = host_resolver.host_by_name(argv[1]); 3. why is everything public in a host? 4. why does both the stream_socket and the socket_connector need to know about the demuxer? Can't the socket_connector ask the stream_socket for its demuxer (I want to simplify usage if possible) 5. can't socket.recv() use something more highlevel than void* and size_t arguments? Why not std::vector<char> ? (The same applies to all the interface functions) best regards Thorsten