rfc2553_connect_to(): Properly detect and log when poll() reached the time out

[privoxy.git] / TODO

diff --git a/TODO b/TODO
index bdd8896..b23841b 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,4 +1,4 @@
-$Id: TODO,v 1.163 2017/05/20 09:25:14 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.
 
 Some Privoxy-related tasks, sorted by the time they
 have been added, not by priority.


@@ -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.
 
      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
 150) Add blacklistd support.
 
 151) Let the dok-tidy target work cross-platform without introducing


@@ -469,8 +466,6 @@ 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
 
      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.
 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.