add design and lbxproxy.def.

Copy first two paragraphs from man page.

3 files changed, 23 insertions, 0 deletions

diff --git a/ChangeLog b/ChangeLog
index e69de29..dd70f7f 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -0,0 +1,5 @@
+2005-09-28  Kristian Høgsberg  <krh@redhat.com>
+
+	* Makefile.am (EXTRA_DIST): add design and lbxproxy.def.
+
+	* README: Copy first two paragraphs from man page.
diff --git a/Makefile.am b/Makefile.am
index 3f7d28d..f87ff42 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -81,3 +81,6 @@ lbxproxy_SOURCES = \
 dist_man1_MANS = \
         lbxproxy.man
 
+EXTRA_DIST = \
+	design \
+	lbxproxy.def
diff --git a/README b/README
index e69de29..1854d36 100644
--- a/README
+++ b/README
@@ -0,0 +1,15 @@
+Applications that would like to take advantage of the Low Bandwidth
+extension to X (LBX) must make their connections to an lbxproxy.
+These applications need to know nothing about LBX, they simply connect
+to the lbxproxy as if were a regular server.  The lbxproxy accepts
+client connections, multiplexes them over a single connection to the X
+server, and performs various optimizations on the X protocol to make
+it faster over low bandwidth and/or high latency connections.
+
+With regard to authentication/authorization, lbxproxy simply passes
+along to the server the credentials presented by the client.  Since X
+clients will connect to lbxproxy, it is important that the user's
+.Xauthority file contain entries with valid keys associated with the
+network ID of the proxy.  lbxproxy does not get involved with how
+these entries are added to the .Xauthority file.  The user is
+responsible for setting it up.