From 4cee52b4fab4efe9fce75872850b22f985c53049 Mon Sep 17 00:00:00 2001 From: Matthieu Herrb Date: Sun, 14 Sep 2008 13:18:31 +0000 Subject: Remove deprecated applications (have been disabled for several month). --- app/lbxproxy/README | 15 --------------- 1 file changed, 15 deletions(-) delete mode 100644 app/lbxproxy/README (limited to 'app/lbxproxy/README') diff --git a/app/lbxproxy/README b/app/lbxproxy/README deleted file mode 100644 index 1854d3624..000000000 --- a/app/lbxproxy/README +++ /dev/null @@ -1,15 +0,0 @@ -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. -- cgit v1.2.3