[Tcl-bugs] [ tcl-Bugs-794839 ] async sockets: readable vs writable fileevents

[SourceForge.net <no...@so...>]

Bugs item #794839, was opened at 2003-08-25 11:43
Message generated for change (Settings changed) made by davygrvy
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110894&aid=794839&group_id=10894

>Category: 27. Channel Types
Group: = 8.3.3
Status: Open
Resolution: None
Priority: 5
Submitted By: Ralf Fassel (ralfixx)
>Assigned to: David Gravereaux (davygrvy)
Summary: async sockets: readable vs writable fileevents

Initial Comment:
Try to async-connect to a host/port which refuses the

connection:



    proc foo {fd} {

      puts "$fd: errstat [fconfigure -error $fd]"

      close $fd

    }



    # chose any port which is not open on local machine

    set port_not_open 65432

    set fd [socket -async localhost $port_not_open]



Now we need some means to get informed when the

conection is

available, the manpage tells use to use fileevent.



I find that on IRIX both readable and writable

fileevents work to

detect the failed connection:



  fileevent $fd readable [list foo $fd]

  fileevent $fd writable [list foo $fd]



both immediately show the failed connection.



However on Windows, only the `writable' fileevent

triggers, the

`readable' just hangs around forever.  The same goes

for connection

timeouts (host offline): readable fileevents do not

time out,

`writables' do.



David Gravereaux said: "... I agree this is a problem.

Please post this bug to the sourceforge bug db."



So here we are...



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110894&aid=794839&group_id=10894