Boost.Asio 套接字析构函数关闭连接? [英] Boost.Asio socket destructor closes connection?

问题描述

boost::asio::ip::tcp::socket 的析构函数究竟做了什么?即使在搜索 Boost 文档和源代码之后，我也无法判断是否需要使用

What exactly does the destructor of boost::asio::ip::tcp::socket do? I can't tell, even after scouring Boost docs and source code, if I need to use

socket->shutdown(boost::asio::ip::tcp::socket::shutdown_both);
socket->close();

打电话之前

delete socket;

我需要手动关闭套接字，还是由析构函数处理?

Do I need to close the socket manually, or does the destructor handle this?

推荐答案

当一个socket被销毁时，它会被socket.close(ec) 在破坏套接字.

When a socket is destroyed, it will be closed as-if by socket.close(ec) during the destruction of the socket.

I/O 对象，例如 socket，派生自 basic_io_object.在 basic_io_object destructor, destroy() 将在 I/O 对象的 I/O 服务上调用，传入 I/O 对象的 implementation_type 实例O 对象的服务将运行.在套接字的情况下，destroy() 将在满足 SocketService 类型要求，关闭底层socket.在下面的文档中，a 是套接字服务类的实例，b 是套接字服务类的 implementation_type 的实例:

I/O objects, such as socket, derive from basic_io_object. Within the basic_io_object destructor, destroy() will be invoked on the I/O object's I/O service, passing in an instance of the implementation_type on which the I/O object's service will operate. In the case of socket, destroy() will be invoked on a type that fulfills the SocketService type requirement, closing the underlying socket. In the documentation below, a is an instance of a socket service class, and b is an instance of the implementation_type for the socket service class:

a.destroy(b):

[...] 隐式取消异步操作，就像调用 a.close(b, ec).

[...] Implicitly cancels asynchronous operations, as if by calling a.close(b, ec).

a.close(b, ec):

如果 a.is_open() 为真，则导致所有未完成的异步操作尽快完成.取消操作的处理程序应传递错误代码 error::operation_aborted.

If a.is_open() is true, causes any outstanding asynchronous operations to complete as soon as possible. Handlers for cancelled operations shall be passed the error code error::operation_aborted.

帖子:!a.is_open(b).

这篇关于Boost.Asio 套接字析构函数关闭连接?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！