I've never tried to benchmark it, but I've gotten the following impressions:
- If you use Tight over ssh, it's best to turn off compression. It doesn't
help and just increases the latency.
- Tight really helps over dialin lines, but over anything faster
Hextile+compression is faster and seems to have
less latency.
- Tight causes more update artifacts than Hextile. (Stuff that should be
updated and is left behind instead.)
These are just things I've noticed in casual use.
-----Original Message-----
From: Michael March [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 30, 2001 2:59 PM
To: [EMAIL PROTECTED]
Subject: Re: Silly Question...
Is it just me or does Hextile encoding with SSH compression seem to work
better than any version of Tight?
> One version of TridaVNC, at least, has a "Tight" encoding option that
works
> better over dialin lines than the standard Hextile encoding.
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
