Version 3 of socket -async

Purpose

This page is dedicated to the asyncroneous socket connect, started by 'socket -async'. See the socket page for a general description.

It also serves as communication page for development and compares current TCL 8.5.15, TCL 8.6.1 and future versions.

Async connect got more complicated in TCL 8.6, as multiple destination IPs are internally supported (due to IPV6 or DNS lookup resulting in multiple IPs).

Command behaviour

socket -async

'socket -async' host first does a syncroneous DNS lookup.

Then the connect is started as background process.

• In TCL8.5, this terminates without any interaction by background processes.
• In TCL8.6, the event loop or command invocation is required to check multiple IPs.

update,vwait

Starting the event loop allows in TCL8.6 to continue with the next try or to fail finally

fileevent writable

Fires when async connect terminates with success or error.

fileevent readable

Fires when async connect terminates with error.

blocking gets,read,puts

The async connect is terminated syncroneously.

On success, the operation is performed.

On connect failure, the connect error is returned by the command. (still to discuss)

non blocking gets,read,puts

The async connect state is checked or continued (next IP) in a non-blocking way.

Possible results:

Implementation status:

fconfigure

Any fconfigure command on the socket continues the connect process.

fconfigure -error

An final connect error should be returned by 'fconfigure -error'. No error should be flagged while connection is running.

Implementation status:

fconfigure -sockname

My own IP of the socket connection. Returns list of IP, Name, Port.

Since IPV6, this value may change within connect tries from "127.0.0.1" to "::1". Also the port may change.

Implementation status:

Idea: The connection process should not be reflected. A compatibility value or an error should returned while connecting.

If we reflect the connection process, we would have issues later, if we would push the connect process to an own thread.

fconfigure -peername

The destination IP. Returns list of IP, Name, Port.

Since IPV6, this value may change within connect tries. Also the port may change (if auto).

Implementation status:

Idea: The connection process should not be reflected. A compatibility value or an error should returned while connecting.

TIPs

Behaviour of fconfigure -peername, -sockname, -error

A discussion tip on the behaviour of those commands while connecting was drafted

fconfigure -errorno

A possibility to return the full POSIX information of a background error was drafted.

Bugs

Win connect ignored

Bug 336441ed59

When a connect terminates to quick so the notifier is not ready jet, the connect is ignored and thus it waits forever for it.

Test is missing.

One may use an IP which fails quickly by definition.

Empty error message on close on failed background flush

Bug 97069ea11a

Fix available.

The test is still difficult, as an async connect must fail after a puts is issued on the channel.

Idea: write a dummy channel driver, which may be set to an error state by fconfigure -seterror and where the readbale/writable state may be set. So one could:

set h [open dummy]
fconfigure $h -seterror EWOULDBLOCK
fileevent $h writable {set x writable}
fconfigure $h -blocking 0
puts $h abc
fconfigure $h -setwritable 1
vwait x
catch {close $h} e d

ToDo's

The branch of Bug 13d3af3ad5 requires fine tuning.

The current test failures on windows are:

==== socket-14.7.2 pending [socket -async] and blocking [gets], no listener FAILED
==== Contents of test case:

        set sock [socket -async localhost [randport]]
        catch {gets $sock} x
        list $x [fconfigure $sock -error]

---- Result was:
{error reading "sock01B57690": connection refused} {}
---- Result should have been (glob matching):
{error reading "sock*": socket is not connected} {connection refused}
==== socket-14.7.2 FAILED



==== socket-14.11.0 pending [socket -async] and blocking [puts], no listener, no flush FAILED
==== Contents of test case:

        set sock [socket -async localhost [randport]]
        fconfigure $sock -blocking 0
        puts $sock ok
        fileevent $sock writable {set x 1}
        vwait x
        close $sock

---- Result was:
socket is not connected
---- Result should have been (exact matching):
broken pipe
==== socket-14.11.0 FAILED



==== socket-14.11.1 pending [socket -async] and blocking [puts], no listener, flush FAILED
==== Contents of test case:

        set sock [socket -async localhost [randport]]
        fconfigure $sock -blocking 0
        puts $sock ok
        flush $sock
        fileevent $sock writable {set x 1}
        vwait x
        close $sock

---- Result was:
socket is not connected
---- Result should have been (exact matching):
broken pipe
==== socket-14.11.1 FAILED