Author: Rob Andrews
Date: 25-09-02 16:45
Yes, tightvnc is a better server depending on your circumstances. But the article doesn't mention where tightvnc is better than normal vnc.
Firstly, tightvnc includes JPEG compression. This makes a huge difference if you're viewing a remote desktop over, say, a 56k dialup. The difference was astounding enough for me to be able to use a 1024x768x32bpp at a superb speed.
Under *nix-type systems, you can enable the "tight" encoding from the viewer command line. I'm not a Windows user, so I can't tell you where it is in the GUI version, but from the commandline:
$ xvncviewer -encodings tight -quality 0 <hostname:port>
This will produce noticeable JPEG compression artifacts, but your session will be faster if you're over a low-bandwidth network.
There is, lastly, one more VNC in the pipeline. Tridia VNC (http://www.tridiavnc.com/) supplies a server with the "tight" encoding for low-bandwidth networks, and also wraps the connection in an SSL tunnel, so you get the benefit of an encrypted connection as well. Worth a look at.
Oh, and whilst you're playing with VNC, take a look at krfb (http://www.tjansen.de/krfb/). I don't know if it's reached FreeBSD ports, but it's definately got prospects. Being able to use a proper XFree86-accelerated desktop locally, and still be able walk away and pick up that same session remotely has great benefits.
|
|
