Thanks for the help... It's working now, and I'm playing with it some
more.
I'm not sure if it matters, but in connection.hpp, in the connection
constructor, there's a bit of code like
try {
socket_.set_option(tcp::no_delay(true)); // Don't delay
writing
} catch (system::system_error & e) {
handler_.log(e.what());
}
And the set_option call *always* seems to throw
boost::asio::error::bad_descriptor. Not sure if it matters.
One other thing I noticed (and don't personally care about) is the
cpp-netlib coding style, like curly brace placement. I'm not sure if
there are boost coding guidelines or not, or if they are enforced or
not, but cpp-netlib looks a little different than other boost source
code. Again, I'm perfectly happy with however it is, but if the goal is
to move cpp-netlib into boost and boost cares (I don't know that either
of those assumptions are true), it's probably easier to start doing it
"the boost way" sooner rather than later.
Thanks
Erik
------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
Cpp-netlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cpp-netlib-devel
