Should --warm option also trigger onload callbacks

[philippjfr]

The --warm option is helpful in warming up a server by running imports and populating potential caches before the first user hits the application being served. Currently it simply creates a fake session causing it to load, however for many apps expensive calculation may occur behind an onload callback, i.e. so it only executes after the page is rendered. Since the fake session never receives an event that says the page has rendered any logic behind the onload callback is never executed and therefore isn't "warmed up". So as a policy question should the warm option also trigger any onload events?

[jbednar]

As a user, if I've gone to the trouble of specifying --warm I'd want as many things warmed as possible. It's true that sometimes there are actions on rendering a page that aren't quite kosher to perform if not actually displaying the page to a user. E.g. if an app is counting the number of visitors, the warming will now make that count off by 1. Still, because users don't have to use --warm if they don't like what it does, I do think it's best to execute whatever could practically be executed.