|Title:||Unix test results on socket -async depend on timing and network configuration|
|Submitter:||oehhar||Created on:||2015-05-29 12:52:08|
|Subsystem:||25. Channel System||Assigned To:||nobody|
|Status:||Open||Last Modified:||2015-05-29 12:52:08|
Bug [13d3af3ad] was started as a windows bug and is fixed, but contains many information about the following unix issue. I decided to close the upper bug and continue the discussion for Unix in this thread.
'socket -async' tests all IPs available for a certain host until one succeeds. This list might be quite long if IPV6 is used. The test (failure) may take minuits if internet is involved until microseconds on the localhost.
In the scope of this, it is difficult to test the internal functioning of 'socket -async' and the interaction with other commands gets/read/puts/fconfigure/close/eof.
In addition, the tcl channel system is demanded in a high level, as "E_WOULDBLOCK" is returned internally while the connection is in progress. This may result in a pile of buffered writes and buffered errors, which should show up later.
So the issue of this ticket is:
See also: http://wiki.tcl.tk/39687