Changes between Version 1 and Version 2 of Ticket #1359, comment 7


Ignore:
Timestamp:
Mar 14, 2015 7:59:13 PM (5 years ago)
Author:
user
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1359, comment 7

    v1 v2  
    1515
    1616*Or if you prefer, in 2) you let the user pick {{{min}}} and {{{max}}}.
    17 For determining the next check time you first obtain two values {{{helpFactor1}}} and {{{helpFactor2}}} of a Gaussian random variable centered around the randomization factor {{{factor}}}, set
    18 {{{finalMin := (1-helpFactor1)*checkInterval}}} and
    19 {{{finalMax := (1+helpFactor2)*checkInterval}}} (both helpFactors can be discarded now)
    20 (Assert that {{{finalMin <= finalMax}}})
    21 Then choose {{{wait}}} from a uniform distribution between {{{[finalMin, finalMax]}}}.
    22 (both values can be discarded now)
    23 Finally, you get the {{{scheduledTime = timeLastCheck + wait}}}.
    2417
    25 (Or, with user-set {{{min}}} and {{{max}}} values: Obtain {{{factor}}} from {{{factor := (max-min)/(max+min)}}} and {{{checkInterval := (max+min)/2}}}, then proceed as above. Heck, if you want, you can even provide both options and let the user choose which input method is more intuitive for him, giving the average and a randomization factor, or giving min and max. And the very same calculations can be used to determine the exact wait time per relay which is sent to the respective Bote relay node)
     18The delete messages sould be per-identity too!! (Needed if later tunnel pooling is done)
     19