summaryrefslogtreecommitdiff
path: root/src/or/or.h
diff options
context:
space:
mode:
authorunixninja92 <charlesvt@gmail.com>2013-09-14 21:40:19 +0200
committerNick Mathewson <nickm@torproject.org>2014-03-05 14:29:54 -0500
commit898154f71779a614e2fd100fb45a788b75207efb (patch)
treec87e64fd32e4e42698fa0c2db0ca2174aba693ef /src/or/or.h
parent147a0f31bd72cfd285f7a6e0867b490262469ccd (diff)
downloadtor-898154f71779a614e2fd100fb45a788b75207efb.tar.gz
tor-898154f71779a614e2fd100fb45a788b75207efb.zip
PredictedCircsRelevanceTime: limit how long we predict a port will be used
By default, after you've made a connection to port XYZ, we assume you might still want to have an exit ready to connect to XYZ for one hour. This patch lets you lower that interval. Implements ticket 91
Diffstat (limited to 'src/or/or.h')
-rw-r--r--src/or/or.h3
1 files changed, 3 insertions, 0 deletions
diff --git a/src/or/or.h b/src/or/or.h
index bd038f783c..5ca63e605b 100644
--- a/src/or/or.h
+++ b/src/or/or.h
@@ -3673,6 +3673,9 @@ typedef struct {
* a new one? */
int MaxCircuitDirtiness; /**< Never use circs that were first used more than
this interval ago. */
+ int PredictedCircsRelevanceTime; /** How long after we've seen a request for
+ * a given port, do we want to continue
+ * to make connections to the same port? */
uint64_t BandwidthRate; /**< How much bandwidth, on average, are we willing
* to use in a second? */
uint64_t BandwidthBurst; /**< How much bandwidth, at maximum, are we willing