Peter:
Hello! No, you're not missing anything. The echoWare/echoServer
protocol is currently all-TCP, so it has the latency issues you describe
(same issues an SSH forwarder would have). My primary concern with
the 1.x generation was enabling connectivity. The 2.x generation will
attempt UDP channels when possible. As you know, UDP packets are
categorically blocked by many commercial-grade firewalls and proxies,
so for those users we'll still rely on TCP as a "fall-back".
I expect the 2.0 release to be in beta within 2 months.
cheers,
Scott
On Jan 14, 2008, at 7:51 AM, Peter Crabtree wrote:
> Scott,
>
> I've been dealing with some latency issues using EchoVNC through an
> echoServer here within the office (moderately loaded 100 mbit
> network), and
> I suddenly realized: the echoServer protocol (whatever it's called)
> runs
> over TCP, right?
>
> But we're transporting the TCP VNC protocol over it, which I've always
> understood (and indeed, experienced, with a TCP-based VPN) that to
> have very
> poor latency as soon as you get any significant packet loss and often
> disconnect problems due to the exponential back-off that gets
> compounded.
>
> Am I missing something here?
>
> --
> Peter
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Echovnc-users mailing list
Echovnc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/echovnc-users
