If you don't like
lbxproxy for some reason: you're not
satisfied with the performance, it doesn't work for you, you don't want
to hassle with creating an lbxproxy for the remote host, or you simply
are interested in trying other options, there is at least one other
package for X protocol compression (anyone have others?)
dxpc works in essentially the same way as LBX. However, to
avoid having to implement an X extension and modify the X server code,
dxpc uses two proxies: one that runs on the REMOTE host, like
lbxproxy, and one that runs on the LOCAL host.
The REMOTE host proxy communicates between the X clients and the LOCAL host proxy, and the LOCAL host proxy communicates between the X server and the REMOTE host proxy.
So, to both the X clients and the X server, it looks like X protocol as usual.
The source for dxpc is available at ftp.x.org.
There is a WWW homepage for dxpc that gives a lot of good information, including pointers to the dxpc mailing list, access to the source code, and a number of pre-built binaries for various platforms:
Ken Chase <email@example.com>
be used for compression. Although its main purpose is to provide
security, it also compresses the data it sends.
Thus, if you run X over a
ssh link you will automatically obtain
some amount of compression.
I don't know. Both LBX and
dxpc are certainly better at raw
ssh. Of course,
ssh provides the added
advantage of security. And of course, there's no reason you can't use
ssh and one of the other two, to get good compression and
It shouldn't be hard to run some benchmarking against these options and get both subjective and statistical measurings of performance. But I haven't done this, and I don't know of anyone who has.