X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=TODO;h=0ef965d24860c65fe33ae3e67d7e0835e60ee7cf;hb=af88dce63a0456ec99cd58eafd4f6021f831b627;hp=5f3047d7beafae07fefa6c0084d068a0f9251a01;hpb=1c229484258e42ea11b72e58c505fc15c9563cbe;p=privoxy.git

diff --git a/TODO b/TODO
index 5f3047d7..0ef965d2 100644
--- a/TODO
+++ b/TODO
@@ -1,6 +1,7 @@
-$Id: TODO,v 1.27 2010/11/22 10:34:06 fabiankeil Exp $
+$Id: TODO,v 1.34 2011/02/10 22:18:30 fabiankeil Exp $
 
-Some Privoxy related task, not ordered in any way.
+Some Privoxy related tasks, sorted by the time they
+have been added, not by priority.
 
 1)  Add some regression tests. Filters should be tested automatically
     (variables too). Could probably reuse large parts of Privoxy-Filter-Test.
@@ -41,9 +42,17 @@ Some Privoxy related task, not ordered in any way.
 
 12) Add pipelining support.
 
-13) Use zlib to compress content before sending it to
+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) Log and filter POST parameters. They can now be logged with
     the noisy debug 32768, but are still not filtered.
 
@@ -229,3 +238,21 @@ Some Privoxy related task, not ordered in any way.
 85) Once #84 is done, write a script that populates a directory with
     various common third-party icons (stumbleupon.png, facebook.png ...)
     and redirect requests for them to Privoxy.
+
+86) Add a server-body-tagger action. This is trivial as as all the
+    functionallity required to do it already exists.
+
+87) Add a client-body-tagger action. This is less trivial as we currently
+    don't buffer client bodies. After 14) is implemented it would be
+    trivial, though.
+
+88) Investigate if there's a Perl module that Privoxy-Regression-Test
+    could optionally use to keep connections alive.
+
+89) When multiple block actions apply, consider showing all the block
+    reasons on the blocked page that haven't been overruled, not just
+    the last one.
+
+90) Implement NO-TAG: patterns that enable a section if the
+    provided pattern doesn't match any TAG. This would make
+    some things cleaner.