aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2012-03-07 21:07:30 -0500
committerRoger Dingledine <arma@torproject.org>2012-03-07 21:07:30 -0500
commitb5a8c3aa00e4acca031ada547a2ac716217832b3 (patch)
treea7a55e81e85c9b5bef83fbdabfc57c355351a39d
parent298e08132f3368514b868eecc5f44e982280010d (diff)
downloadtor-b5a8c3aa00e4acca031ada547a2ac716217832b3.tar.gz
tor-b5a8c3aa00e4acca031ada547a2ac716217832b3.zip
Remove misleading function comment (bug 5324)
In the distant past, connection_handle_read() could be called when there are pending bytes in the TLS object during the main loop. The design since then has been to always read all pending bytes immediately, so read events only trigger when the socket actually has bytes to read. Resolves bug 5324.
-rw-r--r--src/or/connection.c4
1 files changed, 0 insertions, 4 deletions
diff --git a/src/or/connection.c b/src/or/connection.c
index 06a7562656..cbc6091e37 100644
--- a/src/or/connection.c
+++ b/src/or/connection.c
@@ -2595,10 +2595,6 @@ connection_consider_empty_read_buckets(connection_t *conn)
/** Read bytes from conn-\>s and process them.
*
- * This function gets called from conn_read() in main.c, either
- * when poll() has declared that conn wants to read, or (for OR conns)
- * when there are pending TLS bytes.
- *
* It calls connection_read_to_buf() to bring in any new bytes,
* and then calls connection_process_inbuf() to process them.
*