Return to BSD News archive
Newsgroups: comp.os.linux.development.apps,comp.os.linux.development.system,comp.os.linux.hardware,comp.os.linux.setup,comp.os.linux.x,comp.unix.bsd.386bsd.misc,comp.unix.bsd.bsdi.misc,comp.unix.bsd.freebsd.misc,comp.unix.bsd.netbsd.misc Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.ecn.uoknor.edu!paladin.american.edu!gatech!usenet.eel.ufl.edu!newsfeed.internetmci.com!swrinde!sdd.hp.com!hp-pcd!hp-cv!reuter.cse.ogi.edu!qiclab.scn.rain.com!morton!joe From: joe@morton.rain.com (Joe Moss) Subject: Re: Sometimes you need X server source (Was: Why to not buy Matrox Millennium) Message-ID: <Dq4ssL.H8x@morton.rain.com> Organization: Morton & Associates X-Newsreader: NN version 6.5.0 CURRENT #20 References: <4j21ph$crr@slappy.cs.utexas.edu> <4j36ev$prl@news.informatik.uni-oldenburg.de> <4ja099$r8k@ceylon.gte.com> <ragnaroek1996Mar28.063723.8733@news2.compulink.com> <4jkg1l$dl@titan.saturn.net> <ragnaroek1996Apr18.090109.14374@news2.compulink.com> Date: Fri, 19 Apr 1996 22:50:45 GMT Lines: 36 Xref: euryale.cc.adfa.oz.au comp.os.linux.development.apps:14543 comp.os.linux.development.system:21576 comp.os.linux.hardware:36577 comp.os.linux.setup:50887 comp.os.linux.x:29530 comp.unix.bsd.386bsd.misc:636 comp.unix.bsd.bsdi.misc:3256 comp.unix.bsd.freebsd.misc:17504 comp.unix.bsd.netbsd.misc:3083 rockson@idirect.com (jw) writes: >Try reading the X consortium documentation on LBX. As far as I can >tell, all LBX is doing is stream compression using the LZW algorithm. >If you have any documentation that says the opposite, please point it >out to me so that I may stand corrected. You are incorrect. The old version of LBX, that was shipped with X11R6 would change the contents of various packets and then LZW compress the result. For example, the draft of the LBX standard at that time (dated October 23, 1995) listed, in section 2.1, the following layers that client requests went through: 1. Read by LBX and potential byte-swapping 2. Request-specific compression 3. Potential byte swapping 4. Multiplexing of client request streams 5. Delta replacement 6. Stream compression LZW compression was applicable to only layer 6. BTW, LBX no longer uses LZW compression. >What I got out of the documentation is that the LBX driver sits >outside of the server so the server itself is unaware of its >existence. Again, if you have any documentation saying otherwise, >please point it out to me. The lbxproxy program is totally separate from the X server, but it is only used for one end of the link. The other end (the one running the X server) has LBX built-in to the X server as a server protocol extension. -- set Email "joe@morton.rain.com (Joe Moss)";set URL http://psg.com/~joem/