The general idea is we want to be able to experiment with the new path builder such that we can run both new and old implementations side-by-side and compare their results. This would primarily for checking correctness, prior to doing A/B testing.
How this will work depends on how issue 649017 was resolved.
Assuming issue 649017 introducing a new CertVerifier, then we will now want another CertVerifier implementation that dispatches requests to the primary CertVerifier (old), and a secondary CertVerifier (new).
The dual implementation can reply to requests as soon as the primary CertVerifier completes. Completion of the secondary implementation would just be for gathering metrics. (mostly for correctness -- performance comparisons with this approach has issues)
Comment 1 by sheriffbot@chromium.org
, Sep 22 2017Status: Untriaged (was: Available)