|
valium prescription The LBX Mini-HOWTO Paul D. Smith, psmith@baynetworks valium prescription com v1.04, 11 December 1997 LBX (Low Bandwidth X) i valium prescription an X server extension which performs compres sion valium prescription n the X protocol. It is meant to be used in conjunct valium prescription on with X applications and an X server which are sep valium prescription rated by a slow network connection, to improve displ valium prescription y and response time. _______________________________ valium prescription ______________________________________ Table of Cont valium prescription nts 1. Introduction 2. What's The Status Of LBX? 3 valium prescription Who Can Benefit From LBX? 4. Who Doesn't Need LBX? valium prescription 5. How Does LBX Work? 6. What Do I Need To Use LBX? valium prescription 7. What Don't I Need To Use LBX? 8. How Do I Start L valium prescription X? 9. Problems 10. Documentation 11. Alternatives valium prescription 11.1 dxpc - The Differential X Protocol Compressor valium prescription 11.1.1 Advantages 11.1.2 Disadvantages valium prescription 11.1.3 Where Can I Get dxpc? 11.2 Ssh (Secu valium prescription e Shell) 11.3 Which Is Better? _________________ valium prescription ____________________________________________________ valium prescription 1. Introduction Low-Bandwidth X (LBX) attempts to r valium prescription cognize that in this day and age, not everyone will valium prescription e a fast LAN hop or two away from the system that th valium prescription y are running their applications on. The X protocol valium prescription an generate an extraordinary amount of traffic, espe valium prescription ially for simple-seeming things such as creating new valium prescription indows. As anyone who has tried to use X over a dia valium prescription -in modem at 28.8 or even higher can attest, creatin valium prescription new X windows can involve an excruciating wait. LB valium prescription is fundamentally a compression and caching scheme de valium prescription igned to minimize the amount of X traffic generated valium prescription etween two systems. 2. What's The Status Of LBX? A valium prescription of the X Consortium's release of X11R6.3 in December valium prescription 1996, LBX is a full extension to the X protocol. F valium prescription r XFree86 folks, that's XFree86 version 3.3. 3. Wh valium prescription Can Benefit From LBX? If you use a modem to dial in valium prescription o a service provider, then run X applications on rem valium prescription te machines with their DISPLAYs set to your local ma valium prescription hine (or vice versa), LBX will speed up that connecti valium prescription n. Also if you set DISPLAYs from systems across WAN valium prescription (other countries, for example) or other slow links, valium prescription LBX can help. 4. Who Doesn't Need LBX? LBX is usel valium prescription ss, of course, if you're only running applications l valium prescription cally, or if you're not running X at all. Also, if y valium prescription u're running on a fast LAN, LBX won't be much help. valium prescription ome people say "if LBX cuts down on network traffic, valium prescription wouldn't it be good to use even on fast LANs?" It m valium prescription ght be, if your goal is to reduce network traffic. valium prescription ut if your goal is to get better response time LBX p valium prescription obably isn't what you want. Although it does introdu valium prescription e caching and compression, that comes at a cost on b valium prescription th 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. ______________________________________________________________________ REMOTE LOCAL +-----+ +-----+ | APP |-\ Network +----------+ | |\ +-----+ \--------------------------->| X SERVER |=>| || +-----+ / (X Protocol) +----------+ +-----+\ | APP |-/ /_____// +----
|
