diff options
author | Roger Dingledine <arma@torproject.org> | 2009-09-20 19:50:44 -0400 |
---|---|---|
committer | Roger Dingledine <arma@torproject.org> | 2009-09-20 19:50:44 -0400 |
commit | cf2afcd7072d20755ad030ed8240c21ec649dcd7 (patch) | |
tree | 58b8125dd4daaf3ca73eadae47e0e00eeda5ed2d /doc/spec | |
parent | f39bedf250ce878436acda2b7217fa0b5621ffaa (diff) | |
download | tor-cf2afcd7072d20755ad030ed8240c21ec649dcd7.tar.gz tor-cf2afcd7072d20755ad030ed8240c21ec649dcd7.zip |
Fix typos and comments, plus two bugs
A) We were considering a circuit had timed out in the special cases
where we close rendezvous circuits because the final rendezvous
circuit couldn't be built in time.
B) We were looking at the wrong timestamp_created when considering
a timeout.
Diffstat (limited to 'doc/spec')
-rw-r--r-- | doc/spec/proposals/151-path-selection-improvements.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/spec/proposals/151-path-selection-improvements.txt b/doc/spec/proposals/151-path-selection-improvements.txt index af17c4d41a..e0e9e07432 100644 --- a/doc/spec/proposals/151-path-selection-improvements.txt +++ b/doc/spec/proposals/151-path-selection-improvements.txt @@ -90,7 +90,7 @@ Implementation changes in the timeout characteristics. We assume that we've had network connectivity loss if 3 circuits - timeout and we've recieved no cells or TLS handshakes since those + timeout and we've received no cells or TLS handshakes since those circuits began. We then set the timeout to 60 seconds and stop counting timeouts. @@ -100,7 +100,7 @@ Implementation To detect changing network conditions, we keep a history of the timeout or non-timeout status of the past RECENT_CIRCUITS (20) - that successfully completed more than one hop. If more than 75% + that successfully completed at least one hop. If more than 75% of these circuits timeout, we discard all buildtimes history, reset the timeout to 60, and then begin recomputing the timeout. |