Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Subject: Re: CYGWIN SERVER: Some questions From: Robert Collins To: cygdev In-Reply-To: <20010903140332.C23714@cygbert.vinschen.de> References: <20010903140332 DOT C23714 AT cygbert DOT vinschen DOT de> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.13 (Preview Release) Date: 12 Sep 2001 22:50:12 +1000 Message-Id: <1000299013.30377.91.camel@lifelesswks> Mime-Version: 1.0 X-OriginalArrivalTime: 12 Sep 2001 12:37:03.0510 (UTC) FILETIME=[A00FD360:01C13B87] On Mon, 2001-09-03 at 22:03, Corinna Vinschen wrote: > ======================================================================== > FOOD FOR DISCUSSION FOOD FOR DISCUSSION FOOD FOR DISCUSSION > ======================================================================== > > I have some questions about our "Cygwin server project" which is > about to start as soon as we have discussed how to implement > the client/server protocol and how to manage differences between > NT and 9x based OSes. > > The most important question IMO is, how do we design the communication > protocol? It should combine all qualities which can't live together in > reality but only on marketing papers: > - Sockets (Pro: Platform independent, Easy to use, Con: Secure) To address this con: SSPI for NT allows impersonation, and for 95 we simply don't call the NT functions :}. Rob > - Shared memory (Pro: Platform independent, Fast, Con: Secure) > - Named pipes (Pro: Secure, Con: Platform independent) > - DDE (Pro: Platform independent, Secure, Con: Easy to use???) > - RPC (Pro: Platform independent, Secure, Con: Easy to use???) > - COM (Pro: Platform independent, Con: Easy to use???) >