-$Id: TODO,v 1.21 2010/11/06 11:55:49 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.
41) Change documentation framework to one that works cross-platform.
Evaluate WML.
-42) Add DTrace hooks.
+42) Add DTrace hooks. Now that FreeBSD has userland DTrace
+ support there's no longer any reason not to.
43) Write a tool to check URL patterns against URLs in the log file.
This could be included in Privoxy-Regression-Test.
http://coad.measurement-factory.com/details.html#pricing
57) Allow piping into external programs to allow more powerful
- filters and policy decisions.
+ filters and policy decisions. Incomplete support available
+ in Fabian's popen branch.
58) Move more template strings from the code into the actual templates.
80) Change FEATURE_EXTENDED_HOST_PATTERNS to support both
extended and vanilla host patterns at the same time.
+
+ Note that the requirement is to allow the user to decide
+ if the domain pattern should be interpreted as regex or
+ traditional host pattern and if it's not obvious that the
+ user made any decision, default to the latter.
+
+ Possible solutions would be:
+
+ 1. An always-use-regex-domain-patterns config option
+ 2. An enable-regex-domain-patterns-for-this-action-file option
+ 3. An enable-regex-domain-patterns-for-this-action-file-until-the-user-says-otherwise option
+ 4. A treat-the-domain-pattern-in-this-line-as-regex(-or-not) option
+ 5. Combinations of the options above
+
+ With 2+4, 3+4 or 2+3+4 being the preferences until
+ further discussion.
+
+81) Merge Fabian's unlimited-config-lines branch.
+
+82) Detect if the system time goes back in time let the user
+ know if it caused any connections to get closed.
+
+83) Make the FAQ available through the CGI interface like the
+ user manual is.
+
+84) Flesh out the user-manual delivery to serve pages from
+ other directories, too.
+
+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.