[ruby-core:48643] [ruby-trunk - Feature #1644] recv on inherited socket wrapped in TCPSocket does not read data, on Windows

Issue #1644 has been updated by usa (Usaku NAKAMURA).

Description updated
Target version changed from 2.0.0 to Next Major


----------------------------------------
Feature #1644: recv on inherited socket wrapped in TCPSocket does not read data, on Windows
https://bugs.ruby-lang.org/issues/1644#change-32056

Author: kntuaf (Kedar H)
Status: Assigned
Priority: Low
Assignee: usa (Usaku NAKAMURA)
Category: ext
Target version: Next Major


=begin
 On Windows, if you try to wrap an existing winsock socket that was inherited from a parent process into a TCPSocket, any calls to recv on this socket in the child process will not retrieve any data.
 
 This is because the inherited socket is not a member of the internal "socklist" structure in win32.c. rb_w32_select filters out all sockets that are not in this internal list, prior to calling ws2_32!select.
 
 One good solution is for TCPSocket.for_fd to make sure to insert its argument into the socklist structure so that subsequent Winsock functions wrapped by Ruby will work as though the socket were created by this Ruby process. Another possible solution is to expose another method, something like TCPSocket.from_new_fd.
=end



-- 
http://bugs.ruby-lang.org/