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
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Looking for something to work on...
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
content-class: urn:content-classes:message
Date: Tue, 24 Apr 2001 10:44:17 +1000
Message-ID: <EA18B9FA0FE4194AA2B4CDB91F73C0EF79C8@itdomain002.itdomain.net.au>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Looking for something to work on...
Thread-Index: AcDMVniHhmF7eSBSRISh6Gl/J7IXaAAABC6w
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: "John Fortin" <fortinj AT attglobal DOT net>, <cygwin-developers AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id UAA24587

My source is at home, so I can't do much for the next 6 odd hours. I see
two basic approaches to this:

1) implement non-persistent implementations of all things, and then go
for persistence,
2) pickup egors daemon and add to it's API to do what we need.

I don't think we can do proper test cases until 2) is complete. So I'd
suggest grabbing egors daemon code from the cygwin-patches archive and
looking at it.

What we need the daemon to do is one of two things.
Either a) Duplicate two handles from us for each shmid/semid/msgid and
keep the handles open until told to close them - thus keeping win32 from
garbage collecting the resource. Other processes will open the handle
directly without the daemon's help. 
or b) act in a client-server fashion, and do the handle creation and all
management for us.

I prefer a) as there is less serialisation and thus better performance.
There may need to be some system wide syncronisation but I'd rather have
that where we need it, rather than there because of the architecture we
chose.

Rob


> -----Original Message-----
> From: John Fortin [mailto:fortinj AT attglobal DOT net]
> Sent: Tuesday, April 24, 2001 10:41 AM
> To: cygwin-developers AT cygwin DOT com
> Subject: Re: Looking for something to work on...
> 
> 
> 
> > I could actually donate some Windows code that I wrote a 
> few years ago
> > to emulate sys v semaphores.  It wasn't complete but it 
> might be useful
> > as either a starting point or a laughing point.
> > 
> > cgf
> 
> Send it and I'll take a look at it...
> 
> Robert, do you want to break this up between us...  
> 
> John
> 
>