|
snorting valium The LBX Mini-HOWTO Paul D. Smith, psmith@baynetworks.com v1.04, 11 December 1997 LBX (Low Bandwidth X) is an X ser snorting valium er extension which performs compres sion on the X protocol. It is meant to be used in conjunction with X applicat snorting valium ons and an X server which are separated by a slow network connection, to improve display and response time. _______ snorting valium ______________________________________________________________ Table of Contents 1. Introduction 2. What's The Sta snorting valium us Of LBX? 3. Who Can Benefit From LBX? 4. Who Doesn't Need LBX? 5. How Does LBX Work? 6. What Do I Need To Use L snorting valium X? 7. What Don't I Need To Use LBX? 8. How Do I Start LBX? 9. Problems 10. Documentation 11. Alternatives 11 snorting valium 1 dxpc - The Differential X Protocol Compressor 11.1.1 Advantages 11.1.2 Disadvantages 11.1.3 Wh snorting valium re Can I Get dxpc? 11.2 Ssh (Secure Shell) 11.3 Which Is Better? ___________________________________________ snorting valium __________________________ 1. Introduction Low-Bandwidth X (LBX) attempts to recognize that in this day and age, snorting valium ot everyone will be a fast LAN hop or two away from the system that they are running their applications on. The X p snorting valium otocol can generate an extraordinary amount of traffic, especially for simple-seeming things such as creating new wi snorting valium dows. As anyone who has tried to use X over a dial-in modem at 28.8 or even higher can attest, creating new X wind snorting valium ws can involve an excruciating wait. LBX is fundamentally a compression and caching scheme designed to minimize th snorting valium amount of X traffic generated between two systems. 2. What's The Status Of LBX? As of the X Consortium's release snorting valium f X11R6.3 in December, 1996, LBX is a full extension to the X protocol. For XFree86 folks, that's XFree86 version snorting valium .3. 3. Who Can Benefit From LBX? If you use a modem to dial into a service provider, then run X applications on r snorting valium mote machines with their DISPLAYs set to your local machine (or vice versa), LBX will speed up that connection. Als snorting valium if you set DISPLAYs from systems across WANs (other countries, for example) or other slow links, LBX can help. 4. snorting valium Who Doesn't Need LBX? LBX is useless, of course, if you're only running applications locally, or if you're not run snorting valium ing X at all. Also, if you're running on a fast LAN, LBX won't be much help. Some people say "if LBX cuts down on snorting valium etwork traffic, wouldn't it be good to use even on fast LANs?" It might be, if your goal is to reduce network traf snorting valium ic. But if your goal is to get better response time LBX probably isn't what you want. Although it does introduce c snorting valium ching and compression, that comes at a cost on both ends (extra memory for caching, and extra CPU for decompression snorting valium . If your link is fairly speedy LBX will probably result in an overall slowdown. 5. How Does LBX Work? LBX works snorting valium by introducing a proxy server at the client side, which performs caching and compression. The X server knows that t snorting valium e client is using a proxy server, and decompresses accordingly. Here's a normal setup for remote X clients. In our snorting valium discussion, LOCAL is always the workstation sitting in front of you, whose monitor you're looking at, and REMOTE is snorting valium the remote workstation, where the actual application is running. _____________________________________________ snorting valium ________________________ REMOTE LOCAL +-----+ snorting valium +-----+ | APP |-\ Network +----------+ | |\ +-----+ \---- snorting valium ---------------------->| X SERVER |=>| || +-----+ / (X Protocol) +----------+ +-----+\ snorting valium | APP |-/ /_____// +-----+ _________________________________ snorting valium ____________________________________ When using LBX, a proxy server (lbxproxy) is introduced on the remote side, an snorting valium the applications talk to that process instead of directly to the LOCAL server. That process then performs the cach snorting valium ng and compression of X requests and forwards them. It looks like this: __________________________________________ snorting valium ___________________________ REMOTE LOCAL snorting valium +-----+ +-----+ +-------+ Network +----------+ | |\ | snorting valium APP |->| PROXY |----------------------------->| X SERVER |=>| || +-----+ +-------+ (LBX/X Protocol) snorting valium +----------+ +-----+\ +-----+ / /_____// | APP |--/ +----- snorting valium ______________________________________________________________________ Details on exactly what caching and compres snorting valium ion LBX does is beyond the scope of this document. 6. What Do I Need To Use LBX? You need an X server on your LOC snorting valium L system which has the LBX extension compiled in. Unless you explicitly told it not to when building it, X11R6.3 s snorting valium rvers automatically enable LBX. Also, all XFree86 3.3 servers have LBX enabled by default. You can use the xdpyinf snorting valium command to see if your server has the LBX extension: run xdpyinfo and look at the list just under "number of exten snorting valium ions"; you should see "LBX" listed there. Next, you need to get an lbxproxy program compiled for the REMOTE system. snorting valium This is the tricky part. If the remote system is not the same type as your local system, the lbxproxy on your loca snorting valium system will do you no good, of course. There is unfortunately no "broken out" distribution of lbxproxy, so you wi snorting valium l have to either (a) get and build most, if not all, of X11R6.3 for the remote system, or (b) find someplace to get snorting valium pre-compiled lbxproxy binary for your system. The latter is much simpler of course. The lbxproxy is simply a sin snorting valium le executable. There are no configuration files, resource files, etc. associated with it. 7. What Don't I Need To Use LBX? The REMOTE system does not need a new X server (as always, the REMOTE system doesn't need any X server running). The application you want to run does not need to be linked with any special version of X, or any special libraries; I regularly use commercial X11R5 apps over LBX with no trouble. You do not need root or other privileged access on the REMOTE system; the lbxproxy process runs under your normal access permissions. Further, you can run it right from your home directory: it does not have to be installed anywhere. 8. How Do I Start LBX? OK, here it is... after all that it's actually quite simple. Replace LOCAL and REMOTE below with the hostnames of your local workstation and remote system, respectively (don't get them mixed up!) On LOCAL: 1. Start your X server. 2. Tell yo
|
