Skip to main content

SILENCE_SUSTAIN_AFTER

Constant SILENCE_SUSTAIN_AFTER 

Source
pub const SILENCE_SUSTAIN_AFTER: Duration;
Expand description

How long data can go out with nothing at all coming back before the Entry sustains the counterparty’s SURBs on its own: three seconds.

A counterparty that was replying replies at the rate of the data it receives, so three seconds of data going out and nothing coming back, neither a reply, nor a report, nor any other packet, means that its consumption is invisible: its stock may be draining into a return path that delivers nothing, and the balancer, which learns the level from those replies and reports, cannot see it and would mint nothing. Reports alone do not tell that: the Exit sends one every surb_balance_notify_period, 15 s by default, so a Session the Exit does not answer (an upload) is quiet for most of every period without anything being wrong. Hence the sustain needs a reply stream that stopped; see REPLY_STREAM_WINDOW and silence_sustain.