pcrs: Request JIT compilation if it's supported

[privoxy.git] / TODO

diff --git a/TODO b/TODO
index d4b792d..4165e27 100644 (file)
--- a/TODO
+++ b/TODO
@@ -125,10 +125,6 @@ https://www.privoxy.org/faq/general.html#DONATE
 
     Interested donors: 1.
 
 
     Interested donors: 1.
 

-54) Move away from CVS to a more modern revision control system.
-    The move to git is work in progress:
-    https://sourceforge.net/p/ijbswa/mailman/message/34994343/
-

 58) Move more template strings from the code into the actual templates.
 
 59) Import the German template translation.
 58) Move more template strings from the code into the actual templates.
 
 59) Import the German template translation.


@@ -151,8 +147,7 @@ https://www.privoxy.org/faq/general.html#DONATE
 
 66) Stop hard-coding the number of action and filter files.
 
 
 66) Stop hard-coding the number of action and filter files.
 

-67) Clean up source code directory layout. Depends on 54 so
-    we don't lose the revision history.
+67) Clean up source code directory layout.

 
 68) Use standard make syntax so we don't depend on GNU make.
 
 
 68) Use standard make syntax so we don't depend on GNU make.
 


@@ -183,25 +178,6 @@ https://www.privoxy.org/faq/general.html#DONATE
 
 79) Evaluate pcre alternatives.
 
 
 79) Evaluate pcre alternatives.
 

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

 82) Detect if the system time goes back in time let the user
     know if it caused any connections to get closed.
 
 82) Detect if the system time goes back in time let the user
     know if it caused any connections to get closed.
 


@@ -248,7 +224,7 @@ https://www.privoxy.org/faq/general.html#DONATE
     go through all filters and skip the filter types the caller isn't
     interested in.
 
     go through all filters and skip the filter types the caller isn't
     interested in.
 

-98) When showing action section on the CGI pages, properly escape
+98) When showing action sections on the CGI pages, properly escape

     line breaks so they can be copy&pasted into action files without
     adjustments.
 
     line breaks so they can be copy&pasted into action files without
     adjustments.
 


@@ -446,6 +422,20 @@ https://www.privoxy.org/faq/general.html#DONATE
      performance point of view, using a single thread should reduce Privoxy's
      memory footprint a bit which may be noticeable in case of multi-user setups
      with hundreds of idle connections.
      performance point of view, using a single thread should reduce Privoxy's
      memory footprint a bit which may be noticeable in case of multi-user setups
      with hundreds of idle connections.

+
+161) Properly support requests with chunked transfer-encoding with https inspection.
+
+162) When https inspecting, delete generated keys and certificates if
+     the connection to the destination could not be established.
+     Makes silly DoS attacks slightly more complicated.
+
+163) Use subdirectories in the certificate-directory to lower the number
+     of files per directory.
+
+164) Evaluate switching from pcreposix(3) to pcre's native api
+     for URL matching which allows to compile the patterns once
+     at load-time.
+

 ##########################################################################
 
 Hosting wish list (relevant for #53)
 ##########################################################################
 
 Hosting wish list (relevant for #53)


@@ -456,8 +446,7 @@ What we need:
 - Mailinglists (Mailman with public archives preferred)
 - Webspace (on a Unix-like OS that works with the webserver targets
   in GNUMakefile)
 - Mailinglists (Mailman with public archives preferred)
 - Webspace (on a Unix-like OS that works with the webserver targets
   in GNUMakefile)

-- Source code repositories (currently CVS, but migrating away
-  from it is TODO #54 anyway and shouldn't be too much trouble)
+- Git repositories

 - Commit mails (preferably with unified diffs)
 
 (Unsorted) details to look at when evaluating hosters:
 - Commit mails (preferably with unified diffs)
 
 (Unsorted) details to look at when evaluating hosters: