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:	<04f601c0e9d2$21217a60$0200a8c0@lifelesswks>
From:	"Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To:	"cygdev" <cygwin-developers AT cygwin DOT com>
References:	<20010531124452 DOT G1870 AT cygbert DOT vinschen DOT de> <041801c0e9c0$23a3e4b0$0200a8c0 AT lifelesswks> <20010531145957 DOT H1870 AT cygbert DOT vinschen DOT de>
Subject:	Re: [RFD]: Egor's proposal for a Cygwin server process
Date:	Thu, 31 May 2001 23:03:46 +1000
MIME-Version:	1.0
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:	31 May 2001 12:55:13.0472 (UTC) FILETIME=[EEC4D400:01C0E9D0]

----- Original Message -----
From: "Corinna Vinschen" <vinschen AT redhat DOT com>
>
> > Most importantly: I think that the daemon interface needs a
some-what fo
> > rmal API for us in the peanut gallery that want to be able to add
calls
> > to it in the future.
>
> Yep, that's too. But be aware that the interface to the server
> process is only meant to be used INSIDE of Cygwin. For example,
> the `seteuid()' call could be implemented as a call to the
> server in future:
>
> int
> seteuid (uid_t uid)
> {
>   if (os_being_run == winNT)
>     {
>       cygsrv_message msg;
>       msg.set_message_type (CYGSRV_SETEUID);
>       msg.add_ulong_parameter (uid);
>       msg.call_cygwin_server ();
>       return msg.get_int_result ();
>     }
>   ...
> }

I presume you use NT only there because seteuid was your example?

> and the cygsrv_message class would implement the actual protocol.

And the interface to that is an API. Sure it's a private API, but all
the same it's an API. Thats what I'm suggesting should be clearly
setout. (Not necessarily on day 1, but before I get back into IPC :])

Rob

> Corinna
>
> --
> Corinna Vinschen                  Please, send mails regarding Cygwin
to
> Cygwin Developer
mailto:cygwin AT cygwin DOT com
> Red Hat, Inc.
>

- Raw text -