|
valium side effects The LBX Mini-HOWTO Paul D. Smith, psmith@bay valium side effects etworks.com v1.04, 11 December 1997 LBX (Lo valium side effects Bandwidth X) is an X server extension which valium side effects erforms compres sion on the X protocol. It valium side effects is meant to be used in conjunction with X ap valium side effects lications and an X server which are separated valium side effects by a slow network connection, to improve dis valium side effects lay and response time. _____________________ valium side effects _____________________________________________ valium side effects __ Table of Contents 1. Introduction 2. Wh valium side effects t's The Status Of LBX? 3. Who Can Benefit Fr valium side effects m LBX? 4. Who Doesn't Need LBX? 5. How Does valium side effects LBX Work? 6. What Do I Need To Use LBX? 7. valium side effects hat Don't I Need To Use LBX? 8. How Do I Sta valium side effects t LBX? 9. Problems 10. Documentation 11. A valium side effects ternatives 11.1 dxpc - The Differential X valium side effects Protocol Compressor 11.1.1 Advantages valium side effects 11.1.2 Disadvantages 11.1.3 Wher valium side effects Can I Get dxpc? 11.2 Ssh (Secure Shell) valium side effects 11.3 Which Is Better? ___________________ valium side effects _____________________________________________ valium side effects ____ 1. Introduction Low-Bandwidth X (LBX) valium side effects attempts to recognize that in this day and ag valium side effects , not everyone will be a fast LAN hop or two valium side effects away from the system that they are running t valium side effects eir applications on. The X protocol can gene valium side effects ate an extraordinary amount of traffic, espe valium side effects ially for simple-seeming things such as creat valium side effects ng new windows. As anyone who has tried to valium side effects se X over a dial-in modem at 28.8 or even hi valium side effects her can attest, creating new X windows can in valium side effects olve an excruciating wait. LBX is fundament valium side effects lly a compression and caching scheme designed valium side effects to minimize the amount of X traffic generate valium side effects between two systems. 2. What's The Status valium side effects f LBX? As of the X Consortium's release of X valium side effects 1R6.3 in December, 1996, LBX is a full exten valium side effects ion to the X protocol. For XFree86 folks, th valium side effects t's XFree86 version 3.3. 3. Who Can Benefi valium side effects From LBX? If you use a modem to dial into a valium side effects service provider, then run X applications on valium side effects remote machines with their DISPLAYs set to yo valium side effects r local machine (or vice versa), LBX will sp valium side effects ed up that connection. Also if you set DISP valium side effects AYs from systems across WANs (other countries valium side effects for example) or other slow links, LBX can h valium side effects lp. 4. Who Doesn't Need LBX? LBX is useles valium side effects , of course, if you're only running applicati valium side effects ns locally, or if you're not running X at al valium side effects . Also, if you're running on a fast LAN, LBX won't be much help. Some people say "if LBX cuts down on network traffic, wouldn't it be good to use even on fast LANs?" It might be, if your goal is to reduce network traffic. But if your goal is to get better response time LBX probably isn't what you want. Although it does introduce caching and compression, that comes at a cost on both ends (extra memory for caching, and extra CPU for decompression). If your link is fairly speedy LBX will probably result in an overall slowdown. 5. How Does LBX Work? LBX works by introducing a proxy server at the client side, which performs caching and compression. The X server knows that the client is using a proxy server, and decompresses accordingly. Here's a normal setup for remote X clients. In our discussion, LOCAL is always the workstation sitting in front of you, whose monitor you're looking at, and REMOTE is the remote workstation, where the actual application is running. ______________________________________________________________________
|
