On Fri, Jun 08, 2007 at 02:46:19AM +0800, Samuel Thibault wrote: >Lev Bishop, le Thu 07 Jun 2007 14:39:17 -0400, a ?crit : >> On 6/7/07, 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 is... >> bash-3.2$ ./socat TCP-LISTEN:5001 PIPE & exec >> 99<>/dev/tcp/127.0.0.1/5001 ; time for (( a=0; a<1000; a++ )); do echo >> $a >&99; read <&99; done; exec 99>&- >> [1] 4492 >> >> real 0m1.959s >> user 0m0.062s >> sys 0m0.172s >> bash-3.2$ >> [1]+ Done ./socat TCP-LISTEN:5001 PIPE >> >> ...about 2ms round-trip. How is this a problem? > >This adds up to the screen reader latency, etc. > >Really, we tried both, and while tcp/ip was a bit painful, local sockets >were smooth.
What about unix domain sockets in cygwin? It sounds like you think they aren't available. cgf -- 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/