X-Spam-Check-By: sourceware.org
Date: Thu, 7 Jun 2007 11:37:20 -0700
From: Gary Johnson <garyjohn AT spk DOT agilent DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: [ANNOUNCEMENT] New package: brltty 3.8
Message-ID: <20070607183719.GA24707@suncomp1.spk.agilent.com>
Mail-Followup-To: cygwin AT cygwin DOT com
References: <4666819A DOT 52A6488D AT dessent DOT net> <20070606192445 DOT GG6500 AT implementation> <20070606201111 DOT GA2366 AT ednor DOT casa1 DOT cgf DOT cx> <20070607114950 DOT GA3958 AT implementation> <20070607122642 DOT GA31803 AT trixie DOT casa DOT cgf DOT cx> <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>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20070607174554.GH4110@implementation>
User-Agent: Mutt/1.5.15 (2007-04-06)
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

On 2007-06-08, Samuel Thibault wrote:
> Lev Bishop, le Thu 07 Jun 2007 13:41:44 -0400, a écrit :
> > ...around 80MByte/sec, which maybe isn't as fast as it could be using
> > native functionality, but surely brltty doesn't need *that* much
> > bandwidth for transferring text?
> 
> It doesn't need bandwidth, it needs latency.

Latency shouldn't be a problem, either.  We run lots of applications 
here over TCP/IP, many of which have critical latency requirements, 
and have no problem.  Look at VOIP.  It's used on some intra-office 
phone systems without any latency problems that I know of.  I'm 
editing this message in an instance of vim running on a computer in 
a room half-way across the building.  When I press a key, it is 
echoed to my screen "instantaneously" as far as my human senses can 
tell.

TCP/IP should be plenty good for your application, with the 
advantage that you could use one mechanism, one piece of code, to 
access the local machine as well as remote machines.

Regards,
Gary

-- 
Gary Johnson                 | Agilent Technologies
garyjohn AT spk DOT agilent DOT com     | Mobile Broadband Division
                             | Spokane, Washington, USA

--
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/