Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Tue, 5 Mar 2002 12:37:29 +0100 (CET)
From:	Ivan Szanto <szivan AT bitbybit-is DOT nl>
To:	cygwin AT cygwin DOT com
Subject:	Re: Hang problem related to signals and process priority
In-Reply-To:	<Pine.LNX.4.21.0203041108020.5026-200000@appel.bitbybit>
Message-ID:	<Pine.LNX.4.21.0203051219440.11324-100000@appel.bitbybit>
MIME-Version:	1.0

Hi,


Is there a way to quickly check if data is available
for read in a tcp socket without blocking the program?

If there is one, we could use that instead of the overly 
complex signal handling method that sometimes also results
in process hangs, which I reported in my previous mail.

Yes, select and poll could be used to do such a check, but
it looks to me that they are not quick. Or am I wrong in this?
Could someone please help me out here?


thanks a lot,

Ivan
-- 


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -