Date: Wed, 14 Oct 2009 13:47:52 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Passing file descriptors over a socket
Message-ID: <20091014174752.GA8678@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <4AD55408 DOT 9070902 AT cwilson DOT fastmail DOT fm>  <4AD5647C DOT 4040209 AT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4AD5647C.4040209@gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Wed, Oct 14, 2009 at 06:41:16AM +0100, Dave Korn wrote:
>Charles Wilson wrote:
>
>> If not, what sort of "not" is it? (a) possible, but nobody has had the
>> time or inclination to implement (b) not possible on win32 (c) possible,
>> but REALLY hard -- case (a) on steroids.
>
>  Well, there's going to be DuplicateHandle involved in it, to copy the
>underlying os handle into the new process, but that's going to be the
>trivially easy bit.  The real *tricky* part is likely going to be marshalling
>the corresponding fhandler_* objects across process boundaries.  That plus
>there will probably be some required support to handle these fds and how they
>interact across process groups, close-on-exec, fork and exec, etc., etc., -
>all the usual tricky areas.

And, also what happens if you're communicating between two different versions
of cygwin.

cgf

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