mirror of
https://github.com/meteor/meteor.git
synced 2026-05-02 03:01:46 -04:00
f1a7455d4c
Other approaches seemed to be heuristics that broke down in edge cases: a timeout wasn't guaranteed if your JS was slow; page.load in PhantomJS wasn't firing reliably because of long polling.
31 lines
1.2 KiB
JavaScript
31 lines
1.2 KiB
JavaScript
// We want to provide a deteriministic indicator of when the page is 'done'
|
|
// This is non-trivial: e.g. an infinite stream of tweets is never done.
|
|
//
|
|
// We do this instead:
|
|
// We are done sometime after all initial subscriptions are ready
|
|
// Initial subscriptions are those started in the top-level script execution,
|
|
// or from a Meteor.startup callback when Meteor.startup is called in
|
|
// top-level script execution.
|
|
//
|
|
// Note that we don't guarantee that we won't wait longer than we have to;
|
|
// extra subscriptions may be made, and extra data past the minimum may be
|
|
// received.
|
|
//
|
|
// We set this 'started' flag as Package.spiderable.Spiderable._initialSubscriptionsStarted
|
|
// This is used by our phantomjs to determine when the subscriptions are started;
|
|
// it then polls until all subscriptions are ready.
|
|
|
|
Spiderable._initialSubscriptionsStarted = false;
|
|
|
|
var startupCallbacksDone = function () {
|
|
Spiderable._initialSubscriptionsStarted = true;
|
|
};
|
|
|
|
// This extra indirection is how we get called last
|
|
var topLevelCodeDone = function () {
|
|
// We'd like to use Meteor.startup here I think, but docs/behaviour of that is wrong
|
|
Meteor._setImmediate(function () { startupCallbacksDone(); });
|
|
};
|
|
|
|
Meteor.startup(function () { topLevelCodeDone(); });
|