boost::asio and socket ownership

Question

I've two classes (Negotiator, Client), both has their own boost::asio::ip::tcp::socket. Is there a way to transfer socket object to Client after negotiation is finished. I'm looking forward to do something like that:

 boost::asio::ip::tcp::socket sock1(io);
 //...
 boost::asio::ip::tcp::socket sock2;
 sock2.assign(sock1);

This operation must guarantee that the connection won't be closed when sock1 is destroyed.

score 2 · Answer 1 · answered Jun 03 '10 at 15:47

2

Create the socket on the heap (new), and pass the pointer from the negotiator to the client.

answered Jun 03 '10 at 15:47

Dan

3,485
2
21
25

This doesn't help in the case of accepting a plain TCP socket and then wanting to turn it into an ssl socket. Then you truly need to pull the internal socket out of the first and stick it into the second. – Arvid Aug 25 '11 at 05:16

score 2 · Accepted Answer · answered Jun 03 '10 at 18:36

I think that you could:

obtain sock1's native handle with the native() member function
dup() (or WSADuplicateSocket()) sock1's native handle
pass the dup()-ed handle to sock2 with the assing() member function

However:

I'm not sure as I never tried that
If you want to transfer (instead of sharing) the socket from Negotiator to Client, Dan's suggestion of using dynamic allocation is probably simpler, using unique_ptr (or auto_ptr)

score 0 · Answer 3 · answered Feb 13 '18 at 00:17

0

As of the current version of Boost, you would now get the handle with

boost::asio::ip::tcp::socket::my_socket;
auto my_handle = my_socket.native_handle();

instead of the old native() member function.

answered Feb 13 '18 at 00:17

Riot

15,723
4
60
67

boost::asio and socket ownership

3 Answers3

Linked