From: Florian Weimer <fw@deneb.enyo.de>
Subject: Re: Gnat.Sockets and non-blocking connects
Date: Sun, 29 Jun 2003 15:42:19 +0200
Date: 2003-06-29T15:42:19+02:00 [thread overview]
Message-ID: <87he69j8zo.fsf@deneb.enyo.de> (raw)
In-Reply-To: MPG.1968f971473a807b989729@News.CIS.DFN.DE
Jano <nono@celes.unizar.es> writes:
> I'm trying to determine if a asynchronous connect has failed. When it
> ends successfully, I detect it with a select checking for writeability.
> However, it seems I must check the exception set to detect failure.
No, this is a misunderstanding. The exception set is not for error
reporting, but for exceptional situations.
Errors are reported by the R/W selectors. However, nonblocking
connect error reporting is not portable, see Steven's UNIX Network
Programming.
next prev parent reply other threads:[~2003-06-29 13:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-29 12:26 Gnat.Sockets and non-blocking connects Jano
2003-06-29 13:42 ` Florian Weimer [this message]
2003-06-29 14:17 ` Samuel Tardieu
2003-06-29 14:29 ` Florian Weimer
2003-06-29 18:07 ` Jano
2003-06-29 20:50 ` Florian Weimer
2003-06-29 21:13 ` Samuel Tardieu
2003-06-29 21:27 ` Florian Weimer
2003-06-29 22:38 ` Samuel Tardieu
2003-06-29 23:00 ` Jano
2003-06-29 23:00 ` Jano
2003-06-30 15:07 ` Jano
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox