We'd like to simplify this class. Some of these may require us to abort all scanning if we find they are used.
The idea is to sacrifice some preload hits while simplifying the code / reducing CPU usage (ideally).
Initial candidates for removal/simplification:
1. Base urls
2. Rewind points
How else can we reduce the scope of the scanner without regressing performance? What can we measure?
Comment 1 by csharrison@chromium.org
, May 13 2016