<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
<TITLE>The LBX Mini-HOWTO: How Does LBX Work?</TITLE>
<LINK HREF="LBX-6.html" REL=next>
<LINK HREF="LBX-4.html" REL=previous>
<LINK HREF="LBX.html#toc5" REL=contents>
</HEAD>
<BODY>
<A HREF="LBX-6.html">Next</A>
<A HREF="LBX-4.html">Previous</A>
<A HREF="LBX.html#toc5">Contents</A>
<HR>
<H2><A NAME="s5">5. How Does LBX Work?</A></H2>
<P>LBX works by introducing a <EM>proxy server</EM> at the client side,
which performs caching and compression. The X server knows that the
client is using a proxy server, and decompresses accordingly.
<P>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.
<P>
<BLOCKQUOTE><CODE>
<HR>
<PRE>
REMOTE LOCAL
+-----+ +-----+
| APP |-\ Network +----------+ | |\
+-----+ \--------------------------->| X SERVER |=>| ||
+-----+ / (X Protocol) +----------+ +-----+\
| APP |-/ /_____//
+-----+
</PRE>
<HR>
</CODE></BLOCKQUOTE>
<P>When using LBX, a proxy server (<CODE>lbxproxy</CODE>) is introduced on the
remote side, and the applications talk to that process instead of
directly to the LOCAL server. That process then performs the caching
and compression of X requests and forwards them. It looks like this:
<P>
<BLOCKQUOTE><CODE>
<HR>
<PRE>
REMOTE LOCAL
+-----+
+-----+ +-------+ Network +----------+ | |\
| APP |->| PROXY |----------------------------->| X SERVER |=>| ||
+-----+ +-------+ (LBX/X Protocol) +----------+ +-----+\
+-----+ / /_____//
| APP |--/
+-----+
</PRE>
<HR>
</CODE></BLOCKQUOTE>
<P>Details on exactly what caching and compression LBX does is beyond
the scope of this document.
<P>
<P>
<HR>
<A HREF="LBX-6.html">Next</A>
<A HREF="LBX-4.html">Previous</A>
<A HREF="LBX.html#toc5">Contents</A>
</BODY>
</HTML>
