Reduce code duplication in bind_port_helper()

[privoxy.git] / TODO

diff --git a/TODO b/TODO
index e20372d..6c0938d 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,4 +1,4 @@
-$Id: TODO,v 1.41 2011/04/16 17:30:36 fabiankeil Exp $
+$Id: TODO,v 1.47 2011/07/04 17:48:11 fabiankeil Exp $
 
 Some Privoxy related tasks, sorted by the time they
 have been added, not by priority.
@@ -42,17 +42,6 @@ have been added, not by priority.
 
 12) Add pipelining support.
 
-13) Use zlib to deflate content before sending it to
-    the client. Measure if it makes a difference.
-
-    Update:
-    Note that this is already being worked on and mostly done
-    for buffered content and internal CGI responses.
-
-    The difference it does make, seems to be that it slows things
-    down if the client and Privoxy are running on the same system,
-    so for most users enabling it will make no sense.
-
 14) Allow to filter POST parameters.
 
 15) If trusted CGI pages are requested without trusted referrer,
@@ -165,12 +154,12 @@ have been added, not by priority.
 
 65) Polish Website. Probably involves ditching the Docbook
     mess in favour of wml. There should be already some threads
-    in the mailinglists archives about this.
+    in the mailinglists archives about this. See also #41.
 
 66) Increase maximum number of action and filter files.
 
-67) Clean up directory layout. Depends on 54 so we don't
-    lose the revision history.
+67) Clean up source code directory layout. Depends on 54 so
+    we don't lose the revision history.
 
 68) Use standard make syntax so we don't depend on GNU make.
 
@@ -255,3 +244,18 @@ have been added, not by priority.
     be reasonable to default to a limit of one and showing an error
     message if the request for the redirect URL would be redirected
     again.
+
+92) The statistics currently aren't calculated correctly by Privoxy
+    as each thread is only counted as one request which is no longer
+    correct. This should be fixed, or the statistic code removed.
+    Privoxy-Log-Parser's provides more detailed statistics, anyway.
+
+93) Add a config directive to let Privoxy explicitly request either
+    IPv4 (or IPv6) addresses, even if the system supports both.
+    Could be useful as a workaround for misconfigured setups where the
+    libc returns IPv6 addresses even if there's no IPv6 connectivity.
+
+94) Add a config directive to let Privoxy prefer either IPv4 (or IPv6)
+    addresses, instead of trusting the libc to return them in an order
+    that makes sense. Like #93, this could be useful as a workaround
+    for misconfigured setups.