aboutsummaryrefslogtreecommitdiff
path: root/src/or/networkstatus.c
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2011-03-25 17:21:16 -0400
committerNick Mathewson <nickm@torproject.org>2011-03-25 18:32:28 -0400
commitd38030381b04263f76ce7f8ed2d6ceefc4ce363f (patch)
tree0dd112906caf0fcfb71dbcc29a5d0867b8b25a91 /src/or/networkstatus.c
parent550749555cd57a1f82fe6c08e866ae14456ed439 (diff)
downloadtor-d38030381b04263f76ce7f8ed2d6ceefc4ce363f.tar.gz
tor-d38030381b04263f76ce7f8ed2d6ceefc4ce363f.zip
Clarify some documentation and comments wrt resetting OR token buckets
Diffstat (limited to 'src/or/networkstatus.c')
-rw-r--r--src/or/networkstatus.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/src/or/networkstatus.c b/src/or/networkstatus.c
index 18cb4779e0..4f6fe15409 100644
--- a/src/or/networkstatus.c
+++ b/src/or/networkstatus.c
@@ -1747,7 +1747,8 @@ networkstatus_set_current_consensus(const char *consensus,
routerstatus_list_update_named_server_map();
cell_ewma_set_scale_factor(options, current_consensus);
- /* XXX022 where is the right place to put this call? */
+ /* XXXX023 this call might be unnecessary here: can changing the
+ * current consensus really alter our view of any OR's rate limits? */
connection_or_update_token_buckets(get_connection_array(), options);
circuit_build_times_new_consensus_params(&circ_times, current_consensus);