aboutsummaryrefslogtreecommitdiff
path: root/libraries/libproxy/README
diff options
context:
space:
mode:
Diffstat (limited to 'libraries/libproxy/README')
-rw-r--r--libraries/libproxy/README8
1 files changed, 8 insertions, 0 deletions
diff --git a/libraries/libproxy/README b/libraries/libproxy/README
new file mode 100644
index 0000000000..75ae88bd65
--- /dev/null
+++ b/libraries/libproxy/README
@@ -0,0 +1,8 @@
+libproxy (proxy configuration library)
+
+libproxy exists to answer the question: Given a network resource,
+how do I reach it? It handles all the details, enabling you to get
+back to programming. GNOME? KDE? Command line? WPAD? PAC? Network
+changed? It doesn't matter! Just ask libproxy what proxy to use: you
+get simple code and your users get correct, consistant behavior and
+broad infrastructure compatibility.