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 Message-ID: <066c01c0ea1c$d84e06f0$0200a8c0@lifelesswks> From: "Robert Collins" To: References: <20010531124452 DOT G1870 AT cygbert DOT vinschen DOT de> <48146951254 DOT 20010531164356 AT logos-m DOT ru> <20010531140636 DOT E23914 AT redhat DOT com> Subject: Re: [RFD]: Egor's proposal for a Cygwin server process Date: Fri, 1 Jun 2001 07:58:36 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit 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 21:50:02.0053 (UTC) FILETIME=[A50DB750:01C0EA1B] ----- Original Message ----- From: "Christopher Faylor" > >Cross-platform support: > >1. Smoke signals. :) > >2. Shared memory. > >3. Sockets. (don't forget, user may want to use cygwin on machine with > >no networking installed) > >4. Named pipes (nt/2000 only) > > > >a communication between client and server is restricted to local host > >only, so, i suppose, we can take "mixed" approach -- use named pipes > >on nt/2000 and shared memory on w9x. > > > >but first, i'd try to do some performance testing. > > I wouldn't expect a high amount of throughput from the smoke signals but > they do fall right in line with the cygwin computer heating features. Open source to the rescue... I plan to sell an add-on kit for desktop and tower PC's to allow them to achieve the heat levels needed for smoke signalling. Laptops only need to apply SAP to the exterior, so I see no market there. Rob > > cgf >