-$Id: TODO,v 1.2 2009/06/03 18:49:18 fabiankeil Exp $
+$Id: TODO,v 1.11 2010/01/24 15:37:39 fabiankeil Exp $
Some Privoxy related task, not ordered in any way.
macros with strstr() before compiling pcrs commands.
Investigated, needs some restructuring but is probably worth it.
-51) Make user-manual directive more general to allow serving
+51) Make user-manual directive more generic to allow serving
the FAQ and other stuff, too. Consider changing the port
for "same origin policy" issues.
-53) Find a more reliable hoster.
+53) Find a more reliable hoster. Involves finding out what our
+ requirements are and which SF alternatives fulfil them.
+ It would probably also make sense to look into what other
+ projects did when migrating away from SF.
54) Move away from CVS to a more modern revision control system.
software projects" for the Co-Advisor HTTP compliance tests:
http://coad.measurement-factory.com/details.html#pricing
-57) Allow piping into external filter programs.
+57) Allow piping into external programs to allow more powerful
+ filters and policy decisions.
58) Move more template strings from the code into the actual templates.
71) Allow to listen on multiple addresses without having to
bind to all.
+
+73) Factor FEATURE_CONNECTION_SHARING out of
+ FEATURE_CONNECTION_KEEP_ALIVE so the later can be enabled
+ on platforms without mutex support as well.
+
+74) Let Privoxy-Regression-Test optionally check that action
+ sections which disable actions actually are preceded by
+ sections that enable said actions.
+
+75) Create a tool that creates Privoxy action (and filter?) files
+ out of adblock files. Could be implemented as option for
+ url-pattern-translator.pl.