#658 socket -async problem on Win32

obsolete: 8.0.4
closed-fixed
nobody
2
2001-03-31
2000-10-26
Anonymous
No

OriginalBugID: 893 Bug
Version: 8.0.4
SubmitDate: '1998-12-03'
LastModified: '1999-02-02'
Severity: MED
Status: Released
Submitter: welch
ChangedBy: stanton
OS: All
OSVersion: NA
Machine: NA
FixedDate: '1999-02-02'
FixedInVersion: 8.0.5
ClosedDate: '2000-10-25'

I ran into a problem when doing an asynchronous connect on Windows.
If the connect fails, you never get notified that the connect failed.
The problem is that FD_CONNECT is not watched for.

I also added a small feature to help with asynchronous connects. Once
the connect fails, there was no reasonable way to tell that it failed
or to get an error message. You could determine that the connect failed
(on Unix only before the fix) by trying to write a 0 byte string to the
socket, and it would fail if the connect failed. However, you still
couldn't tell why the connect failed. I added a fconfigure option that
will give the status of the connect.

fconfigure sockid -error

will return an error string representing the error condition. If there
was no error condition, this will return an empty string. Here is the
patch for both things.

Patch on the web

Discussion

  • Brent B. Welch

    Brent B. Welch - 2000-10-26
    • priority: 5 --> 2
    • status: open --> closed-fixed
     
  • Don Porter

    Don Porter - 2001-03-31
    • labels: 104250 --> 27. Channel Types