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
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Mon, 1 Jul 2002 12:59:16 -0400 (EDT)
From:	David E Euresti <davie AT MIT DOT EDU>
To:	<cygwin AT cygwin DOT com>
Subject:	Re: Patch to pass file descriptors
Message-ID:	<Pine.GSO.4.30L.0207011247001.17206-100000@biohazard-cafe.mit.edu>
MIME-Version:	1.0

So,
	There's the option of keeping full BSD semantics if the cygserver
is running.  I like that.  I can require users to run the cygserver.  I
don't mind.
	Unfortunately the whole net.cc has been refactored so I'll have to
regenerate my patch.
	The question is, can you incorporate my code and then you guys
deal with the case when the cygserver isn't running?  I don't really have
a use for a non cygserver solution because my program depends on full BSD
semantics.  Such as closing the handle after sending it, or exiting the
process after sending it.  I don't see how to solve this second problem
without the cygserver.
	I'm sure other people will want full BSD semantics also so why not
allow them to have it if the cygserver is running.

By the way, I thought about how to solve the problem of the program
closing the handle after sending it.  Assuming that you'll spawn a thread
with your shared memory stuff.  You can dup the handle in that thread.
Then the sender can do whatever it wants with it's copy (Close it), and
when the receiver has it, it can tell the sender to release it.
Unfortunately this won't help the situation where the sender process
exits before the receiver receives.

	Also should this discussion be moved to cygwin-developers?

David


--
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 -