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
Date: Fri, 23 Mar 2001 15:57:42 +0300
From: Egor Duda <deo AT LOGOS-M DOT RU>
X-Mailer: The Bat! (v1.45) Personal
Reply-To: Egor Duda <cygwin-developers AT cygwin DOT com>
Organization: DEO
X-Priority: 3 (Normal)
Message-ID: <1783665564.20010323155742@logos-m.ru>
To: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
CC: cygwin-developers AT cygwin DOT com
Subject: Re: setup will have to wait :[
In-reply-To: <001b01c0b397$2d1ca720$0200a8c0@lifelesswks>
References: <001b01c0b397$2d1ca720$0200a8c0 AT lifelesswks>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi!

Friday, 23 March, 2001 Robert Collins robert DOT collins AT itdomain DOT com DOT au wrote:

RC> For those interested in the "how" side, I'm planning on avoiding named
RC> pipes (due to the horror stories I've heard about win 9x).
RC> Instead I plan on using a manual reset named event object and a named
RC> mutex. The mutex will control access, and the event object will control
RC> syncronisation. (I.e if process 2 opens & tries to write, it will
RC> successfuly get the mutex, and then wait for the event object to be
RC> pulsed. It will then "write" the data. The recieving process will
RC> recieve the mutex when the first process completes the write. That then
RC> gets repeated.

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.

Egor.            mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19