ooni / netx / 269

100%

push

travis-ci

Make events actionable for OONI's nervous system (#78)

After trial and error, I have determined that, in general, to decide
whether we need follow-up measurements, we need just the result of
four events in the HTTP round trip:

- RESOLVE_DONE
- CONNECT
- HANDSHAKE_DONE
- ROUND_TRIP_DONE

In some cases it may be possible to run operations inline while in
others it's probably best to run concurrently or later.

Regardless of the implementation strategy, this diff makes sure that
by combining this four events only, we have enough information to
conclude whether to trigger more measurements.

This conclusion is based on my analysis using ooni/jafar, it may be
of course that later we'll need to tweak this a bit.

I've been doing refactoring for quite some time to prepare this.

Master issue: https://github.com/ooni/probe-engine/issues/87

11 of 11 new or added lines in 3 files covered. (100.0%)

1400 of 1400 relevant lines covered (100.0%)

43.52 hits per line