Commit 55cb83f3 authored by Josh Soref's avatar Josh Soref

spelling: necessarily

parent 50f1fd36
...@@ -234,7 +234,7 @@ IOFetch::operator()(boost::system::error_code ec, size_t length) { ...@@ -234,7 +234,7 @@ IOFetch::operator()(boost::system::error_code ec, size_t length) {
return; return;
// On Debian it has been often observed that boost::asio async // On Debian it has been often observed that boost::asio async
// operations result in EINPROGRESS. This doesn't neccessarily // operations result in EINPROGRESS. This doesn't necessarily
// indicate an issue. Thus, we continue as if no error occurred. // indicate an issue. Thus, we continue as if no error occurred.
} else if (ec && (ec.value() != boost::asio::error::in_progress)) { } else if (ec && (ec.value() != boost::asio::error::in_progress)) {
logIOFailure(ec); logIOFailure(ec);
......
...@@ -97,7 +97,7 @@ public: ...@@ -97,7 +97,7 @@ public:
// error code, but simply wait for the connection to get // error code, but simply wait for the connection to get
// established before the handler is invoked. It turns out, however, // established before the handler is invoked. It turns out, however,
// that on some OSes the connect handler may receive this error code // that on some OSes the connect handler may receive this error code
// which doesn't neccessarily indicate a problem. Making an attempt // which doesn't necessarily indicate a problem. Making an attempt
// to write and read from this socket will typically succeed. So, // to write and read from this socket will typically succeed. So,
// we ignore this error. // we ignore this error.
if (ec.value() != boost::asio::error::in_progress) { if (ec.value() != boost::asio::error::in_progress) {
......
...@@ -358,7 +358,7 @@ TEST(TCPSocket, sequenceTest) { ...@@ -358,7 +358,7 @@ TEST(TCPSocket, sequenceTest) {
EXPECT_EQ(TCPCallback::OPEN, client_cb.called()); EXPECT_EQ(TCPCallback::OPEN, client_cb.called());
// On some operating system the async_connect may return EINPROGRESS. // On some operating system the async_connect may return EINPROGRESS.
// This doesn't neccessarily indicate an error. In most cases trying // This doesn't necessarily indicate an error. In most cases trying
// to asynchronously write and read from the socket would work just // to asynchronously write and read from the socket would work just
// fine. // fine.
if ((client_cb.getCode()) != 0 && (client_cb.getCode() != EINPROGRESS)) { if ((client_cb.getCode()) != 0 && (client_cb.getCode() != EINPROGRESS)) {
......
...@@ -139,7 +139,7 @@ public: ...@@ -139,7 +139,7 @@ public:
// EINPROGRESS error code, but simply wait for the connection // EINPROGRESS error code, but simply wait for the connection
// to get established before the handler is invoked. It turns out, // to get established before the handler is invoked. It turns out,
// however, that on some OSes the connect handler may receive this // however, that on some OSes the connect handler may receive this
// error code which doesn't neccessarily indicate a problem. // error code which doesn't necessarily indicate a problem.
// Making an attempt to write and read from this socket will // Making an attempt to write and read from this socket will
// typically succeed. So, we ignore this error. // typically succeed. So, we ignore this error.
if (ec.value() != boost::asio::error::in_progress) { if (ec.value() != boost::asio::error::in_progress) {
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment