I
Iñaki Baz Castillo
Hi, perhaps I miss something but when I close a TCP connection using=20
TCPSocket#close the connection remains as OS level for long seconds (minute=
s).
Be reading the doc:
IO#close
Closes ios and flushes any pending writes to the operating system. The
stream is unavailable for any further data operations; an IOError is rais=
ed
if such an attempt is made. I/O streams are automatically closed when they
are claimed by the garbage collector.
So, does it mean that the TCP connection is *really* terminated when the=20
garbage collector removes it (some seconds/minutes after calling=20
TCPSocket#close)?
Unfortunatelly it's not valid for me, I need the capability to close a TCP=
=20
connection and open a new one without mantaining two parallel connections.
Any other way to really close a TCP connection at OS level? Thanks.
=2D-=20
I=C3=B1aki Baz Castillo <[email protected]>
TCPSocket#close the connection remains as OS level for long seconds (minute=
s).
Be reading the doc:
IO#close
Closes ios and flushes any pending writes to the operating system. The
stream is unavailable for any further data operations; an IOError is rais=
ed
if such an attempt is made. I/O streams are automatically closed when they
are claimed by the garbage collector.
So, does it mean that the TCP connection is *really* terminated when the=20
garbage collector removes it (some seconds/minutes after calling=20
TCPSocket#close)?
Unfortunatelly it's not valid for me, I need the capability to close a TCP=
=20
connection and open a new one without mantaining two parallel connections.
Any other way to really close a TCP connection at OS level? Thanks.
=2D-=20
I=C3=B1aki Baz Castillo <[email protected]>