X-Git-Url: http://www.privoxy.org/gitweb/contact.html?a=blobdiff_plain;f=TODO;h=b23841bcf237291e243b7ef3a368cb1161ca86ef;hb=1e3471c05f279e9f4ebead3a943512d8919a70f3;hp=4f1eca27be3fc14aa6d3ee0c67b5ad9424e2dc59;hpb=f12bac5985029c40e6760d99d30c084397c58c81;p=privoxy.git diff --git a/TODO b/TODO index 4f1eca27..b23841bc 100644 --- a/TODO +++ b/TODO @@ -1,4 +1,4 @@ -$Id: TODO,v 1.160 2017/03/08 13:16:08 fabiankeil Exp $ +$Id: TODO,v 1.165 2017/05/29 10:40:28 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. @@ -439,9 +439,6 @@ http://www.privoxy.org/faq/general.html#DONATE currently can result in client requests to config.privoxy.org on the Internet which may not be desirable. -149) Use poll() for socket selection so the number of sockets Privoxy - can deal with isn't limited to FD_SETSIZE anymore. - 150) Add blacklistd support. 151) Let the dok-tidy target work cross-platform without introducing @@ -469,6 +466,14 @@ http://www.privoxy.org/faq/general.html#DONATE to the one used for ftp. Motivation: https://lists.privoxy.org/pipermail/privoxy-users/2017-March/000195.html +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)