-$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.
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.
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.