Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "Bob Byrnes" <byrnes AT curl DOT com>
Date: Wed, 15 Dec 2004 10:50:21 -0500
In-Reply-To: <20041214123758.GK22056@cygbert.vinschen.de> from Corinna Vinschen (Dec 14,  1:37pm)
Organization: Curl Corporation
X-Address: 1 Cambridge Center, 10th Floor, Cambridge, MA 02142-1612
X-Phone: 617-761-1238
X-Fax: 617-761-1201
To: cygwin AT cygwin DOT com
Subject: Re: [Fwd: unison and cygwin on windows xp SP2]
Message-Id: <20041215155021.0F80BE5DD@wildcard.curl.com>

> any new development on the pipe frontier?

I haven't had as much time to work on this as I would have hoped,
due to a confluence of short-term deadlines at work and elsewhere.
But some of these projects are now done, so I have hope for an
improved rate of progress.

My plan is still to use one of the NtQuery* calls to distinguish the
real case when a pipe buffer is getting full from the bogus case when
FilePipeLocalInformation bizarrely reports that the available space in the
buffer is reduced just because there is a blocked *read* on an empty pipe.
This is what's bothering sftp and I think unison, although I have not yet
had a chance to directly observe the latter (the problem with sftp is,
in contrast, quite clear).

I think I know how to do this, but I need to finish experimenting with
some prototype code that I have been playing with.

I'm sorry this has taken so long ... stay tuned.

--
Bob

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/