cgi_show_client_tags(): Fix a harmless 'dead store' warning

[privoxy.git] / TODO

diff --git a/TODO b/TODO
index 04baa29..bdd8896 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,4 +1,4 @@
-$Id: TODO,v 1.158 2017/03/08 13:11:25 fabiankeil Exp $
+$Id: TODO,v 1.163 2017/05/20 09:25:14 fabiankeil Exp $
 
 Some Privoxy-related tasks, sorted by the time they
 have been added, not by priority.
@@ -414,7 +414,7 @@ http://www.privoxy.org/faq/general.html#DONATE
      forward-override). Investigate and fix or document.
 
 141) Port Privoxy to CloudABI, which, despite the name, is actually
-     rather neet. https://github.com/NuxiNL/cloudlibc
+     rather neat. https://github.com/NuxiNL/cloudlibc
 
 142) Remove or update the "internal" pcre version.
 
@@ -460,6 +460,25 @@ http://www.privoxy.org/faq/general.html#DONATE
 154) Underline links in docs and cgi pages. More precisely,
      don't mess with the browser defaults for link underlining.
 
+155) The sig_handler() shouldn't call log_error().
+     While it isn't known to cause actual problems in normal operation,
+     it's technically incorrect and causes crashes when running in
+     valgrind.
+
+156) Reject socks requests with an explicit error message similar
+     to the one used for ftp. Motivation:
+     https://lists.privoxy.org/pipermail/privoxy-users/2017-March/000195.html
+
+157) Add a directive to control the currently hardcoded receive-buffer size.
+
+158) Use a single thread to wait for new requests on reused client connections.
+     Currently the thread that handles the first request on a connection
+     stays responsible for the client connect until it gets closed.
+     In case of lots of idle connections lots of waiting threads are used.
+     While it's conceivable that this ineffiency is irrelevant from a
+     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.
 ##########################################################################
 
 Hosting wish list (relevant for #53)