RouteScience’s Approach to Measurement
We have a unique approach, based on Web traffic
HTML isn’t all traffic, but it’s ubiquitous
For sources and sinks of content, there’s more than enough data in existing traffic
Just watching traffic come and go is fine, but what about alternative paths?
HTML has the curious property that clients ask servers where to find things
Therefore reserve one existing object (usu. a “spacer GIF”) to study performance
As users request content, direct them to the measurement device for the test object, and serve it over alternate paths