gpt4 book ai didi

c++ - boost::asio async_connect 不可取消?

转载 作者:行者123 更新时间:2023-11-30 03:13:34 25 4
gpt4 key购买 nike

短篇小说:socket.async_connect(...) 之后的调用 socket.cancel() 完美运行,即调用了完成处理程序;但是对于 asio::async_connect(socket, ...) 之后的 socket.cancel(),永远不会调用完成处理程序。

长话短说,这里是完整的源代码:

#include <iostream>
#include <vector>
#include <chrono>
#include <ctime>
#include <boost/asio.hpp>

namespace sys = boost::system;
namespace asio = boost::asio;
using tcp = asio::ip::tcp;

static const int count = 10;

struct client_t {
using sock_ptr_t = std::unique_ptr<tcp::socket>;
using resolve_results_t = tcp::resolver::results_type;

client_t(asio::io_context& io_context_): io_context{io_context_}, resolver{io_context}{
}

void start() {
tcp::endpoint endpoint(asio::ip::address::from_string("93.184.216.34"), 80);
resolver.async_resolve("www.example.com", "80", [&](auto ec, auto results){
this->on_resolve(ec, results);
});
}

void on_resolve(const sys::error_code& ec, resolve_results_t results) {
auto now = std::chrono::system_clock::now();
time_t tt = std::chrono::system_clock::to_time_t(now);
std::cerr << "on_resolve " << this << " " << ec.message() << ", at " << ctime(&tt);
if (!ec) {
sock = std::make_unique<tcp::socket>(io_context);
/*
sock->async_connect(*results.begin(), [this](auto& ec){
this->on_connect(ec);
});
*/
asio::async_connect(*sock, results.begin(), results.end(), [this](auto& ec, auto it){
this->on_connect(ec);
});
}
}

void on_connect(const sys::error_code& ec) {
auto now = std::chrono::system_clock::now();
time_t tt = std::chrono::system_clock::to_time_t(now);
std::cerr << "on_connect " << this << " " << ec.message() << ", at " << ctime(&tt);
}


void cancel() {
std::cout << "cancellation attempt for " << this << "\n";
if (sock) {
sys::error_code ec;
sock->cancel(ec);
std::cout << "cancellation result: " << ec.message() << "\n";
}
}

asio::io_context& io_context;
sock_ptr_t sock;
tcp::resolver resolver;

};

using client_ptr_t = std::unique_ptr<client_t>;
using container_t = std::vector<client_ptr_t>;

int main() {
asio::io_context io_context;
std::cerr << "starting\n";

container_t container;
for(int i = 0; i < count; ++i) {
auto client = std::make_unique<client_t>(io_context);
client->start();
container.emplace_back(std::move(client));
}

boost::asio::deadline_timer timer(io_context);

timer.expires_from_now(boost::posix_time::milliseconds(5));
timer.async_wait([&](auto& ec){
for(auto& it : container) {
it->cancel();
}
auto now = std::chrono::system_clock::now();
time_t tt = std::chrono::system_clock::to_time_t(now);
std::cout << "cancelled at " << ctime(&tt);
});

io_context.run();
std::cerr << "finished\n";

return 0;
}

输出样本是:

starting
on_resolve 0x985000 Success, at Sat Oct 26 22:59:22 2019
on_resolve 0x9854c0 Success, at Sat Oct 26 22:59:22 2019
on_resolve 0x985600 Success, at Sat Oct 26 22:59:22 2019
on_resolve 0x985730 Success, at Sat Oct 26 22:59:22 2019
on_resolve 0x985830 Success, at Sat Oct 26 22:59:22 2019
on_resolve 0x985700 Success, at Sat Oct 26 22:59:22 2019
on_resolve 0x985a90 Success, at Sat Oct 26 22:59:22 2019
on_resolve 0x985bb0 Success, at Sat Oct 26 22:59:22 2019
on_resolve 0x985cd0 Success, at Sat Oct 26 22:59:22 2019
on_resolve 0x985e80 Success, at Sat Oct 26 22:59:22 2019
cancellation attempt for 0x985000
cancellation result: Success
cancellation attempt for 0x9854c0
cancellation result: Success
cancellation attempt for 0x985600
cancellation result: Success
cancellation attempt for 0x985730
cancellation result: Success
cancellation attempt for 0x985830
cancellation result: Success
cancellation attempt for 0x985700
cancellation result: Success
cancellation attempt for 0x985a90
cancellation result: Success
cancellation attempt for 0x985bb0
cancellation result: Success
cancellation attempt for 0x985cd0
cancellation result: Success
cancellation attempt for 0x985e80
cancellation result: Success
cancelled at Sat Oct 26 22:59:22 2019

(我必须按 ctrl+c 才能停止程序)。

但是,如果我使用 sock->async_connect(...)(上面代码中的注释部分),一切正常,即

starting                                                                                                                                                                                      
on_resolve 0x6d6000 Success, at Sat Oct 26 22:59:03 2019
on_resolve 0x6d64c0 Success, at Sat Oct 26 22:59:03 2019
on_resolve 0x6d6600 Success, at Sat Oct 26 22:59:03 2019
on_resolve 0x6d6730 Success, at Sat Oct 26 22:59:03 2019
on_resolve 0x6d6830 Success, at Sat Oct 26 22:59:03 2019
on_resolve 0x6d6700 Success, at Sat Oct 26 22:59:03 2019
on_resolve 0x6d6a90 Success, at Sat Oct 26 22:59:03 2019
on_resolve 0x6d6bb0 Success, at Sat Oct 26 22:59:03 2019
on_resolve 0x6d6cd0 Success, at Sat Oct 26 22:59:03 2019
on_resolve 0x6d6e80 Success, at Sat Oct 26 22:59:03 2019
cancellation attempt for 0x6d6000
cancellation result: Success
cancellation attempt for 0x6d64c0
cancellation result: Success
cancellation attempt for 0x6d6600
cancellation result: Success
cancellation attempt for 0x6d6730
cancellation result: Success
cancellation attempt for 0x6d6830
cancellation result: Success
cancellation attempt for 0x6d6700
cancellation result: Success
cancellation attempt for 0x6d6a90
cancellation result: Success
cancellation attempt for 0x6d6bb0
cancellation result: Success
cancellation attempt for 0x6d6cd0
cancellation result: Success
cancellation attempt for 0x6d6e80
cancellation result: Success
cancelled at Sat Oct 26 22:59:03 2019
on_connect 0x6d6000 Operation canceled, at Sat Oct 26 22:59:03 2019
on_connect 0x6d64c0 Operation canceled, at Sat Oct 26 22:59:03 2019
on_connect 0x6d6600 Operation canceled, at Sat Oct 26 22:59:03 2019
on_connect 0x6d6730 Operation canceled, at Sat Oct 26 22:59:03 2019
on_connect 0x6d6830 Operation canceled, at Sat Oct 26 22:59:03 2019
on_connect 0x6d6700 Operation canceled, at Sat Oct 26 22:59:03 2019
on_connect 0x6d6a90 Operation canceled, at Sat Oct 26 22:59:03 2019
on_connect 0x6d6bb0 Operation canceled, at Sat Oct 26 22:59:03 2019
on_connect 0x6d6cd0 Operation canceled, at Sat Oct 26 22:59:03 2019
on_connect 0x6d6e80 Operation canceled, at Sat Oct 26 22:59:03 2019
finished

为什么会这样?我已阅读文档,但没有发现任何提示我做错了什么。

最佳答案

如文档中所述,asio::async_connect

... attempts to connect a socket to one of a sequence of endpoints ... once for each endpoint in the sequence, until a connection is successfully established.

如果提供了多个端点,取消一次未完成的连接尝试将导致 asio::async_connect 从后续端点重试(here's 循环)。

尝试在取消后关闭套接字。这将阻止 asio::async_connect 重试。

        sock->cancel(ec);
sock->close(ec);

关于c++ - boost::asio async_connect 不可取消?,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/58574290/

25 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com