How to do stuff with boomerang

The following is a list of all items identified in the use case document and then some.

HOWTO

• Howto 0 — How to get data out of a beacon/before_beacon event handler
• Howto 1a — User clicks a link on a page we control and page is usable when onload fires
• Howto 1b — User clicks a link on a page we control and page is usable at some developer determined point
• Howto 2 — Measure perceived performance of content loaded dynamically
• Howto 3 — Measure a user's bandwidth/latency along with page load time
• Howto 4 — Measure more than just page load time
• Howto 5 — Request/page tagging
• Howto 6 — Configuring boomerang
• Howto 7 — Protecting the beacon from abuse
• Howto 8 — Measure DNS latency
• Howto 9 — Collect performance data from the W3C Navigation Timing API
• Howto 10 — Load time of a page prerendered by Google Chrome

TODO

• TODO 1 — Measure a random sample of users instead of all users

The latest code and docs is available on github.com/SOASTA/boomerang