socket close vs shutdown

最新推荐文章于 2019-02-22 19:28:34 发布

paragenius

最新推荐文章于 2019-02-22 19:28:34 发布

阅读量550

点赞数

文章标签： socket os

本文链接：https://blog.csdn.net/paragenius/article/details/4816675

版权

        Calling close and shutdown have two different affects on the underlying socket.

        The first thing to point out is that the socket is a resource in the underlying OS and multiple processes can have a handle for the same underlying
        socket.

        When you call close it decrements the handle count by one and if the handle count has reached zero then the socket and associated connection goes through
        the normal close procedure (effectively sending a FIN / EOF to the peer) and the socket is deallocated.

The thing to pay attention to here is that if the handle count does not reach zero because another process still has a handle to the socket then the
vote    connection is not closed and the socket is not deallocated.

        On the other hand calling shutdown for reading and writing closes the underlying connection and sends a FIN / EOF to the peer regardless of how many
        processes have handles to the socket. However, it does not deallocate the socket and you still need to call close afterward.

shutdown可以用于顺序释放socket，避免close时消息丢失。