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: 2013-04-23 08:35:16

#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:  reopened      
 Milestone:  To Be Determined     |   Component:  asio          
   Version:  Boost 1.42.0         |    Severity:  Problem       
Resolution:                       |    Keywords:                
----------------------------------+-----------------------------------------
Changes (by countforall@…):

  * status:  closed => reopened
  * resolution:  fixed =>

Comment:

 Hi,

 I feel this problem is still existing and closed without any solution.
 Currently i am assign native socket after duplicating the original
 socket(Windows). And it has been working for last few months without any
 issues. But found socket issues in duplication in one of the customer
 machine. If i remove duplication and use the original socket, it is
 working fine.but i would lost the connection after boost socket
 destruction.

 Please add a release function to remove the native socket from boost
 socket or add a flag to to tell the destructor not to close the native
 socket.

 Thanks
 mahe

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