gpt4 book ai didi

c++ - boost::asio 接受器在 EOF 后重新打开和异步读取

转载 作者:行者123 更新时间:2023-11-28 00:46:51 25 4
gpt4 key购买 nike

遗憾的是,我的开发停滞了,因为我无法理解应该如何使用 boost::asio::ip::tcp::acceptor。TCPReader 类被设计为单例, header 将以下内容声明为私有(private)。

void runInThread();

void read_handler(const boost::system::error_code &ec, std::size_t bytes_transferred);

void accept_handler(const boost::system::error_code &ec);

boost::asio::io_service io_service;
boost::asio::io_service::work runningService;
boost::asio::ip::tcp::socket sock;
boost::asio::ip::tcp::acceptor acceptor;

bool isConnected;

<<

TCPReader::TCPReader() : sock(io_service),
runningService(io_service),
acceptor(io_service, boost::asio::ip::tcp::endpoint(boost::asio::ip::tcp::v4(), TCPPort)){
this->isConnected = false;

acceptor.async_accept(sock, boost::bind(&TCPReader::accept_handler, this, boost::asio::placeholders::error));
boost::thread thread(boost::bind(&TCPReader::runInThread, this));
}


void TCPReader::runInThread(){
io_service.run();
}

accept_handler 然后触发 read_handler,这一切都像魅力一样工作,直到 read_handler 收到 EOF 或其他错误。我想要的是让接受器回到可以像初始化后那样接受连接的状态。我尝试使用 close()cancel() 以及以下 open()listen()async_accept(就像在构造函数中一样)。但这一切似乎都不起作用。非常感谢您的帮助。

最佳答案

错误发生在对sock 的操作中,而不是acceptor。因此,acceptor 的状态不应该受到影响。它只需要在 sock 处于初始关闭状态时启动 async_accept 操作。

下面是一个监听 12345 端口的完整基本示例:

#include <iostream>

#include <boost/array.hpp>
#include <boost/asio.hpp>

using boost::asio::ip::tcp;

class tcp_reader
{
public:
tcp_reader(boost::asio::io_service& io_service)
: io_service_(io_service),
socket_(io_service),
acceptor_(io_service,
tcp::endpoint(tcp::v4(), 12345))
{
accept_connection();
}

private:

void accept_connection()
{
std::cout << "accepting connection" << std::endl;
// Verify socket is in a closed state.
socket_.close();
// On success or failure, acceptor will open() socket_.
acceptor_.async_accept(socket_,
boost::bind(&tcp_reader::handle_accept, this,
boost::asio::placeholders::error));
}

void handle_accept(const boost::system::error_code& error)
{
// On error, return early.
if (error)
{
std::cout << "handle_accept: " << error.message() << std::endl;
return;
}

// Start reading from socket.
read();
}

void read()
{
std::cout << "reading from socket" << std::endl;
async_read(socket_, boost::asio::buffer(buffer_),
boost::asio::transfer_at_least(1),
boost::bind(&tcp_reader::handle_read, this,
boost::asio::placeholders::error,
boost::asio::placeholders::bytes_transferred));
}

void handle_read(const boost::system::error_code& error,
std::size_t bytes_transferred)
{
// On error, go back to listening for a new connection.
if (error)
{
std::cout << "handle_read: " << error.message() << std::endl;
accept_connection();
return;
}

// Output read data.
std::cout.write(&buffer_[0], bytes_transferred);

// Read data, so read some more.
read();
}

private:
boost::asio::io_service& io_service_;
tcp::socket socket_;
tcp::acceptor acceptor_;
boost::array<char, 1024> buffer_;
};

int main()
{
boost::asio::io_service io_service;
tcp_reader reader(io_service);
io_service.run();
}

使用时,我在一个终端上运行它,连接到端口 12345,发送​​消息,终止连接,然后重新建立连接。服务器控制台输出如下:

[twsansbury@localhost]$ ./a.out accepting connectionreading from sockethelloreading from socketgoodbyereading from sockethandle_read: End of fileaccepting connectionreading from socketoh, oh noreading from sockethandle_read: End of fileaccepting connectionctrl + c

和客户端控制台:

[twsansbury@localhost]$ nc 127.0.0.1 12345hello        goodbye ctrl + c[twsansbury@localhost]$ nc 127.0.0.1 12345oh, oh noctrl + c

需要注意的一个行为细节是,尽管 async_accept 操作可能不会在 acceptor_ 上挂起,但连接仍在排队。因此,如果一个连接已经被接受,而另一个客户端试图连接,那么后者的连接将等待被接受。如果这不是所需的行为,则接受器需要通过 close() 转换出监听状态。 This答案图状态转换并更详细地描述了一些接受者行为。

关于c++ - boost::asio 接受器在 EOF 后重新打开和异步读取,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/15926077/

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