Closed bgrozev closed 3 months ago
The timeline is configurable in the config file but once initialized doesn't change (payload verification does, via an http api). I just renamed ENABLE_TIMELINE
to enableTimeline
because I think that's the usual convention
I'm a little concerned what happens to packets that are in flight at the moment the timeline gets turned on.
Maybe restructure it so that
PacketInfo.timeline
is anEventTimeline?
which only gets instantiated ifenableTimeline
is set, and then everything else checks whether the specific PacketInfo's timeline val is non-null?