This is the mail archive of the
mailing list for the Cygwin project.
Re: [ANNOUNCEMENT] New package: brltty 3.8
Christopher Faylor, le Wed 06 Jun 2007 16:11:11 -0400, a écrit :
> On Thu, Jun 07, 2007 at 03:24:45AM +0800, Samuel Thibault wrote:
> >Brian Dessent, le Wed 06 Jun 2007 02:42:50 -0700, a ?crit :
> >> Yes, setup automatically selects everything in Base for installation,
> >Ah, I didn't know that, is that documented somewhere??
> Yes: http://cygwin.com/cygwin-ug-net/setup-net.html
Mmm, maybe a short note in http://cygwin.com/setup.html would be useful?
> >That would make programming less easy. Brltty can communicate with
> >other (potentially non-cygwin) applications with tcp/ip (remotely) or
> >local pipes (locally, more efficiently). For keeping compatibility
> >with other applications for local pipes, windows pipes are used.
> >Mixing cygwin sockets and windows local pipes is not particularly fun,
> >so that's why we end up just using windows socket and
> >WaitForMultipleObjects() in a separate thread.
> You haven't really described why the linux-like pipe() command is
> inadequate for anything that an application needs.
This application needs to communicate about accessibility with
non-cygwin applications too. Does the linux-like pipe() map 1-1 to
> Merely stating that "mixing cygwin sockets and windows local pipes is
> not... fun" is not really an argument for not doing it.
This was an euphemism for "using select is already tricky, mixing both
a select() for cygwin sockets and WaitForMultipleObjects() for windows
named pipes, and handle the different kinds of sockets, that would be a
Really, for the sake of maintainability, this is a lot simpler.
> Unless there is good reason, the cygwin distribution really is
> supposed to be comprised of programs which use the linux API.
But when talking about communicating with other applications, we need to
use windows interfaces when the linux API doesn't permit it, shouldn't
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html