X-Spam-Check-By: sourceware.org Message-ID: Date: Wed, 4 Jul 2007 23:54:32 -0400 From: "Lev Bishop" To: cygwin@cygwin.com Subject: Re: [ANNOUNCEMENT] New package: brltty 3.8 In-Reply-To: <20070703130416.GD3701@implementation.labri.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Disposition: inline References: <20070606192615.GG22248@trixie.casa.cgf.cx> <2D9E96311DCA4C48BF185EA6928BC7BB01E1BD3E@asc-mail.int.ascribe.com> <20070607115925.GC3958@implementation> <20070702233210.GD3759@interface.famille.thibault.fr> <20070703075424.GI30973@calimero.vinschen.de> <20070703130416.GD3701@implementation.labri.fr> Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id l653sk31001841 On 7/3/07, Samuel Thibault wrote: > Corinna Vinschen, le Tue 03 Jul 2007 09:54:24 +0200, a écrit : > > For using local named pipes you don't need winsock anyway, and for > > remote connections you should use Cygwin sockets. > > And mixing both is quite difficult. Anyhow, I'll only enable cygwin > sockets and hope the latency is sufficient for users. I still feel that if you had latency problems using TCP it was either a bug in your program, or a bug in your protocol (you are the author of the protocol, right?), or a bug in cygwin. Is there a way I can investigate this without needing special braille hardware (like, is there some kind of "dummy" driver that sends the braille to the console or something). Or, do you have a simplified testcase that exhibits this latency you are concerned about? Lev -- 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/