Re: [Boost-bugs] [Boost C++ Libraries] #3900: Request for support of "release" member function or assign without ownership transfer to asio socket

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #3900: Request for support of "release" member function or assign without ownership transfer to asio socket
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2010-03-18 09:39:45

#3900: Request for support of "release" member function or assign without
ownership transfer to asio socket
---------------------------------+------------------------------------------
 Reporter:  artyomtnk@…          |       Owner:  chris_kohlhoff
     Type:  Feature Requests     |      Status:  new           
Milestone:  To Be Determined     |   Component:  asio          
  Version:  Boost 1.42.0         |    Severity:  Problem       
 Keywords:                       |  
---------------------------------+------------------------------------------

Comment(by artyomtnk@…):

 I think you're confusing it with asio::local::stream_protocol::socket.
   If you're using it with null_buffers, posix::stream_descriptor basically
 works
   with anything that is selectable. That means sockets (TCP, UDP, UNIX),
 pipes, and
   a lot more.

 If so, then yes, it would be helpful and for Windows I would just have to
 Duplicate socket before assigning it.

 BTW: Maybe it is possible to provide assign member function I suggested
 before that
 would associate the socket but it would also tell not to close it in dtor
 and thus:

 If system is POSIX or Windows with disable IOCP then, do not call close(),
 otherwise, when using IOCP, attach() would duplicate the socket befor
 calling to
 assign.

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/3900#comment:9>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.