Mail Archives: cygwin-developers/2002/07/04/10:15:15

Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
From: "Robert Collins" <robert DOT collins AT syncretize DOT net>
To: <cygwin-developers AT cygwin DOT com>
Subject: RE: Interruptable connect
Date: Fri, 5 Jul 2002 00:13:13 +1000
Message-ID: <001501c22364$ef66aae0$0200a8c0@lifelesswks>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <>
Importance: Normal

> -----Original Message-----
> From: cygwin-developers-owner AT cygwin DOT com 
> [mailto:cygwin-developers-owner AT cygwin DOT com] On Behalf Of 
> Corinna Vinschen
> Sent: Friday, 5 July 2002 12:11 AM

What about using the non blocking connect call from winsock2 - with an
alert event, and then wait on that event and the interrupt event?

I have some win32 nonblocking network code around here somewhere that
does just that.


- Raw text -

  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019