X-Spam-Check-By: sourceware.org
Date: Fri, 8 Jun 2007 23:05:19 +0800
From: Samuel Thibault <samuel DOT thibault AT ens-lyon DOT org>
To: cygwin AT cygwin DOT com
Subject: Re: [ANNOUNCEMENT] New package: brltty 3.8
Message-ID: <20070608150519.GN4943@implementation>
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20070607160859 DOT GA3577 AT implementation> <20070607163744 DOT GA4972 AT ednor DOT casa1 DOT cgf DOT cx> <20070607164933 DOT GF4110 AT implementation> <ba40711f0706071041u66e12b81k23639ee67332df49 AT mail DOT gmail DOT com> <20070607174554 DOT GH4110 AT implementation> <ba40711f0706071139t6dc53eddl9d3c277a95d56ead AT mail DOT gmail DOT com> <20070607184619 DOT GA14598 AT implementation> <20070607190146 DOT GA5235 AT ednor DOT casa1 DOT cgf DOT cx> <20070608075720 DOT GA4943 AT implementation> <20070608144249 DOT GB26855 AT trixie DOT casa DOT cgf DOT cx>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20070608144249.GB26855@trixie.casa.cgf.cx>
User-Agent: Mutt/1.5.11
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

Christopher Faylor, le Fri 08 Jun 2007 10:42:49 -0400, a écrit :
> On Fri, Jun 08, 2007 at 03:57:20PM +0800, Samuel Thibault wrote:
> >Christopher Faylor, le Thu 07 Jun 2007 15:01:46 -0400, a ?crit :
> >>What about unix domain sockets in cygwin?  It sounds like you think
> >>they aren't available.
> >
> >As I already said several times, it must work with non-cygwin
> >applications as well.
> 
> A unix domain socket used on stdin/stdout works with non-cygwin
> applications.
> 
> It would really help if you provided an actual use case which
> demonstrated what you are talking about.

I'm a bit tired to re-explain all of this, I've already had to do it on
other lists, it's really boring to go along all these arguments just
once more... But since you really want some details, here are more:

Brltty acts as a "braille display server": when an application not only
wants to display their usual GUI, but also braille, it can connect to
brltty for rendering braille (by sending "write" commands, and receiving
"keypress" events). Thus stdin/stdout can't work since applications may
want to keep their text GUI as it is and the initiative of establishing
the connexion comes from the application anyway, not brltty.

> Otherwise, you seem to be asking that we just trust you that brltty is
> different from most other packages in the distribution and deserves
> special dispensation.

I'm not asking so big special dispensation.  Why should cygwin
applications be forced to use cygwin sockets?

Samuel

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