Rephrase a log message in serve(). Client request arrival should be differentiated...

[privoxy.git] / TODO

diff --git a/TODO b/TODO
index 34849f2..68fcfd6 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,4 +1,4 @@
-$Id: TODO,v 1.26 2010/11/06 11:58:16 fabiankeil Exp $
+$Id: TODO,v 1.28 2010/12/14 18:56:11 fabiankeil Exp $
 
 Some Privoxy related task, not ordered in any way.
 
@@ -199,6 +199,22 @@ Some Privoxy related task, not ordered in any way.
 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
@@ -213,3 +229,10 @@ 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.