Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Message-ID: <000501c0b3e9$7fa3d890$0200a8c0@lifelesswks>
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: "Egor Duda" <cygwin-developers AT cygwin DOT com>
Cc: <cygwin-developers AT cygwin DOT com>
References: <001b01c0b397$2d1ca720$0200a8c0 AT lifelesswks> <1783665564 DOT 20010323155742 AT logos-m DOT ru>
Subject: Re: setup will have to wait :[
Date: Sat, 24 Mar 2001 09:34:59 +1100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-OriginalArrivalTime: 23 Mar 2001 22:29:23.0278 (UTC) FILETIME=[B5F34EE0:01C0B3E8]

----- Original Message -----
From: "Egor Duda" <deo AT LOGOS-M DOT RU>
To: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
Cc: <cygwin-developers AT cygwin DOT com>
Sent: Friday, March 23, 2001 11:57 PM
Subject: Re: setup will have to wait :[


> Hi!
>
> Friday, 23 March, 2001 Robert Collins robert DOT collins AT itdomain DOT com DOT au
wrote:
>
>
> RC> For data transfer, I was thinking of using shared named
memory:anyone
> RC> know of caveats for that on win9x?
>
> 1. it won't work with non-cygwin apps.
> 2. the biggest problem with fifo is that there can be several readers
> and several writers. and i don't know how to implement the following
> thing: when all writers die all readers should receive eof. and it
> should work even if writers haven't had a chance to exit gracefully,
> but was killed from taskmanager, for example. Similarly, when all
> readers die, writers should unblock with EPIPE.

1. Do "non-unix" apps understand the concept of a FIFO file? I know that
cygwin already has named pipe support so is there any reason to try and
make FIFO support interoperate (and what should it appear as?)

2. Do you have a reference? So far I've found lots of sys/stat.h header
files :].  If you don't are writes and reads atomic? Do all readers
recieve all the same data from each writer - or do they pair off? (That
sounds rather dirty I know :])

Rob