node/lib/timers.js

246 lines
6.5 KiB
JavaScript
Raw Normal View History

2011-03-10 08:54:52 +00:00
// Copyright Joyent, Inc. and other Node contributors.
//
// Permission is hereby granted, free of charge, to any person obtaining a
// copy of this software and associated documentation files (the
// "Software"), to deal in the Software without restriction, including
// without limitation the rights to use, copy, modify, merge, publish,
// distribute, sublicense, and/or sell copies of the Software, and to permit
// persons to whom the Software is furnished to do so, subject to the
// following conditions:
//
// The above copyright notice and this permission notice shall be included
// in all copies or substantial portions of the Software.
//
// THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
// OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
// MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN
// NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
// DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
// OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE
// USE OR OTHER DEALINGS IN THE SOFTWARE.
var Timer = process.binding('timer_wrap').Timer;
2011-01-18 22:26:32 +00:00
var L = require('_linklist');
2011-01-28 00:59:28 +00:00
var assert = require('assert').ok;
2010-10-26 18:56:32 +00:00
// Timeout values > TIMEOUT_MAX are set to 1.
var TIMEOUT_MAX = 2147483647; // 2^31-1
2010-12-02 04:59:06 +00:00
var debug;
2011-02-04 17:00:21 +00:00
if (process.env.NODE_DEBUG && /timer/.test(process.env.NODE_DEBUG)) {
2010-12-02 04:59:06 +00:00
debug = function() { require('util').error.apply(this, arguments); };
} else {
debug = function() { };
2010-10-26 18:56:32 +00:00
}
2010-12-02 04:59:06 +00:00
// IDLE TIMEOUTS
//
// Because often many sockets will have the same idle timeout we will not
// use one timeout watcher per item. It is too much overhead. Instead
// we'll use a single watcher for all sockets with the same timeout value
// and a linked list. This technique is described in the libev manual:
// http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#Be_smart_about_timeouts
// Object containing all lists, timers
// key = time in milliseconds
// value = list
var lists = {};
2010-10-26 18:56:32 +00:00
// the main function - creates lists on demand and the watchers associated
// with them.
2010-12-02 04:59:06 +00:00
function insert(item, msecs) {
item._idleStart = new Date();
item._idleTimeout = msecs;
2010-10-26 18:56:32 +00:00
2010-10-26 19:52:31 +00:00
if (msecs < 0) return;
2010-10-26 18:56:32 +00:00
var list;
if (lists[msecs]) {
list = lists[msecs];
} else {
list = new Timer();
list.start(msecs, 0);
2011-01-18 22:26:32 +00:00
L.init(list);
2010-10-26 18:56:32 +00:00
lists[msecs] = list;
list.ontimeout = function() {
2010-10-26 18:56:32 +00:00
debug('timeout callback ' + msecs);
2010-10-26 18:56:32 +00:00
var now = new Date();
2010-12-02 04:59:06 +00:00
debug('now: ' + now);
2010-10-26 18:56:32 +00:00
var first;
2011-01-18 22:26:32 +00:00
while (first = L.peek(list)) {
2010-10-26 18:56:32 +00:00
var diff = now - first._idleStart;
if (diff + 1 < msecs) {
list.start(msecs - diff, 0);
2010-12-02 04:59:06 +00:00
debug(msecs + ' list wait because diff is ' + diff);
2010-10-26 18:56:32 +00:00
return;
} else {
2011-01-18 22:26:32 +00:00
L.remove(first);
assert(first !== L.peek(list));
if (!first._onTimeout) continue;
// v0.4 compatibility: if the timer callback throws and the user's
// uncaughtException handler ignores the exception, other timers that
// expire on this tick should still run. If #2582 goes through, this
// hack should be removed.
//
// https://github.com/joyent/node/issues/2631
Domain feature This is a squashed commit of the main work done on the domains-wip branch. The original commit messages are preserved for posterity: * Implicitly add EventEmitters to active domain * Implicitly add timers to active domain * domain: add members, remove ctor cb * Don't hijack bound callbacks for Domain error events * Add dispose method * Add domain.remove(ee) method * A test of multiple domains in process at once * Put the active domain on the process object * Only intercept error arg if explicitly requested * Typo * Don't auto-add new domains to the current domain While an automatic parent/child relationship is sort of neat, and leads to some nice error-bubbling characteristics, it also results in keeping a reference to every EE and timer created, unless domains are explicitly disposed of. * Explicitly adding one domain to another is still fine, of course. * Don't allow circular domain->domain memberships * Disposing of a domain removes it from its parent * Domain disposal turns functions into no-ops * More documentation of domains * More thorough dispose() semantics * An example using domains in an HTTP server * Don't handle errors on a disposed domain * Need to push, even if the same domain is entered multiple times * Array.push is too slow for the EE Ctor * lint domain * domain: docs * Also call abort and destroySoon to clean up event emitters * domain: Wrap destroy methods in a try/catch * Attach tick callbacks to active domain * domain: Only implicitly bind timers, not explicitly * domain: Don't fire timers when disposed. * domain: Simplify naming so that MakeCallback works on Timers * Add setInterval and nextTick to domain test * domain: Make stack private
2012-04-06 23:26:18 +00:00
if (first.domain) {
if (first.domain._disposed) continue;
first.domain.enter();
}
try {
first._onTimeout();
} catch (e) {
if (!process.listeners('uncaughtException').length) throw e;
process.emit('uncaughtException', e);
}
Domain feature This is a squashed commit of the main work done on the domains-wip branch. The original commit messages are preserved for posterity: * Implicitly add EventEmitters to active domain * Implicitly add timers to active domain * domain: add members, remove ctor cb * Don't hijack bound callbacks for Domain error events * Add dispose method * Add domain.remove(ee) method * A test of multiple domains in process at once * Put the active domain on the process object * Only intercept error arg if explicitly requested * Typo * Don't auto-add new domains to the current domain While an automatic parent/child relationship is sort of neat, and leads to some nice error-bubbling characteristics, it also results in keeping a reference to every EE and timer created, unless domains are explicitly disposed of. * Explicitly adding one domain to another is still fine, of course. * Don't allow circular domain->domain memberships * Disposing of a domain removes it from its parent * Domain disposal turns functions into no-ops * More documentation of domains * More thorough dispose() semantics * An example using domains in an HTTP server * Don't handle errors on a disposed domain * Need to push, even if the same domain is entered multiple times * Array.push is too slow for the EE Ctor * lint domain * domain: docs * Also call abort and destroySoon to clean up event emitters * domain: Wrap destroy methods in a try/catch * Attach tick callbacks to active domain * domain: Only implicitly bind timers, not explicitly * domain: Don't fire timers when disposed. * domain: Simplify naming so that MakeCallback works on Timers * Add setInterval and nextTick to domain test * domain: Make stack private
2012-04-06 23:26:18 +00:00
if (first.domain) first.domain.exit();
2010-10-26 18:56:32 +00:00
}
}
2010-10-26 18:56:32 +00:00
debug(msecs + ' list empty');
2011-01-18 22:26:32 +00:00
assert(L.isEmpty(list));
list.close();
delete lists[msecs];
2010-10-26 18:56:32 +00:00
};
}
2011-01-18 22:26:32 +00:00
L.append(list, item);
assert(!L.isEmpty(list)); // list is not empty
2010-10-26 18:56:32 +00:00
}
2010-12-02 04:59:06 +00:00
var unenroll = exports.unenroll = function(item) {
2011-01-18 22:26:32 +00:00
L.remove(item);
2010-10-26 18:56:32 +00:00
2011-01-13 10:22:09 +00:00
var list = lists[item._idleTimeout];
// if empty then stop the watcher
debug('unenroll');
2011-01-18 22:26:32 +00:00
if (list && L.isEmpty(list)) {
2011-01-13 10:22:09 +00:00
debug('unenroll: list empty');
list.close();
delete lists[item._idleTimeout];
2010-10-26 18:56:32 +00:00
}
// if active is called later, then we want to make sure not to insert again
item._idleTimeout = -1;
2010-10-26 18:56:32 +00:00
};
// Does not start the time, just sets up the members needed.
2010-12-02 04:59:06 +00:00
exports.enroll = function(item, msecs) {
// if this item was already in a list somewhere
2010-10-26 18:56:32 +00:00
// then we should unenroll it from that
if (item._idleNext) unenroll(item);
2010-10-26 18:56:32 +00:00
item._idleTimeout = msecs;
2011-01-18 22:26:32 +00:00
L.init(item);
2010-10-26 18:56:32 +00:00
};
2011-01-13 10:22:09 +00:00
// call this whenever the item is active (not idle)
2010-10-26 18:56:32 +00:00
// it will reset its timeout.
2010-12-02 04:59:06 +00:00
exports.active = function(item) {
var msecs = item._idleTimeout;
2010-10-26 19:52:31 +00:00
if (msecs >= 0) {
2010-10-26 18:56:32 +00:00
var list = lists[msecs];
if (!list || L.isEmpty(list)) {
insert(item, msecs);
2010-10-26 18:56:32 +00:00
} else {
item._idleStart = new Date();
2011-01-18 22:26:32 +00:00
L.append(list, item);
2010-10-26 18:56:32 +00:00
}
}
};
2010-10-26 19:52:31 +00:00
/*
* DOM-style timers
*/
2010-12-02 04:59:06 +00:00
exports.setTimeout = function(callback, after) {
var timer;
after = ~~after;
if (after < 1 || after > TIMEOUT_MAX) {
after = 1; // schedule on next tick, follows browser behaviour
}
timer = { _idleTimeout: after };
timer._idlePrev = timer;
timer._idleNext = timer;
if (arguments.length <= 2) {
timer._onTimeout = callback;
2010-10-26 19:52:31 +00:00
} else {
/*
* Sometimes setTimeout is called with arguments, EG
*
* setTimeout(callback, 2000, "hello", "world")
*
* If that's the case we need to call the callback with
* those args. The overhead of an extra closure is not
* desired in the normal case.
*/
var args = Array.prototype.slice.call(arguments, 2);
timer._onTimeout = function() {
callback.apply(timer, args);
2010-10-26 19:52:31 +00:00
}
}
Domain feature This is a squashed commit of the main work done on the domains-wip branch. The original commit messages are preserved for posterity: * Implicitly add EventEmitters to active domain * Implicitly add timers to active domain * domain: add members, remove ctor cb * Don't hijack bound callbacks for Domain error events * Add dispose method * Add domain.remove(ee) method * A test of multiple domains in process at once * Put the active domain on the process object * Only intercept error arg if explicitly requested * Typo * Don't auto-add new domains to the current domain While an automatic parent/child relationship is sort of neat, and leads to some nice error-bubbling characteristics, it also results in keeping a reference to every EE and timer created, unless domains are explicitly disposed of. * Explicitly adding one domain to another is still fine, of course. * Don't allow circular domain->domain memberships * Disposing of a domain removes it from its parent * Domain disposal turns functions into no-ops * More documentation of domains * More thorough dispose() semantics * An example using domains in an HTTP server * Don't handle errors on a disposed domain * Need to push, even if the same domain is entered multiple times * Array.push is too slow for the EE Ctor * lint domain * domain: docs * Also call abort and destroySoon to clean up event emitters * domain: Wrap destroy methods in a try/catch * Attach tick callbacks to active domain * domain: Only implicitly bind timers, not explicitly * domain: Don't fire timers when disposed. * domain: Simplify naming so that MakeCallback works on Timers * Add setInterval and nextTick to domain test * domain: Make stack private
2012-04-06 23:26:18 +00:00
if (process.domain) timer.domain = process.domain;
exports.active(timer);
return timer;
};
2010-10-26 19:52:31 +00:00
2010-12-02 04:59:06 +00:00
exports.clearTimeout = function(timer) {
if (timer && (timer.ontimeout || timer._onTimeout)) {
timer.ontimeout = timer._onTimeout = null;
if (timer instanceof Timer) {
timer.close(); // for after === 0
} else {
exports.unenroll(timer);
}
2010-10-29 07:00:43 +00:00
}
2010-10-26 19:52:31 +00:00
};
2010-12-02 04:59:06 +00:00
exports.setInterval = function(callback, repeat) {
var timer = new Timer();
2010-10-26 19:52:31 +00:00
Domain feature This is a squashed commit of the main work done on the domains-wip branch. The original commit messages are preserved for posterity: * Implicitly add EventEmitters to active domain * Implicitly add timers to active domain * domain: add members, remove ctor cb * Don't hijack bound callbacks for Domain error events * Add dispose method * Add domain.remove(ee) method * A test of multiple domains in process at once * Put the active domain on the process object * Only intercept error arg if explicitly requested * Typo * Don't auto-add new domains to the current domain While an automatic parent/child relationship is sort of neat, and leads to some nice error-bubbling characteristics, it also results in keeping a reference to every EE and timer created, unless domains are explicitly disposed of. * Explicitly adding one domain to another is still fine, of course. * Don't allow circular domain->domain memberships * Disposing of a domain removes it from its parent * Domain disposal turns functions into no-ops * More documentation of domains * More thorough dispose() semantics * An example using domains in an HTTP server * Don't handle errors on a disposed domain * Need to push, even if the same domain is entered multiple times * Array.push is too slow for the EE Ctor * lint domain * domain: docs * Also call abort and destroySoon to clean up event emitters * domain: Wrap destroy methods in a try/catch * Attach tick callbacks to active domain * domain: Only implicitly bind timers, not explicitly * domain: Don't fire timers when disposed. * domain: Simplify naming so that MakeCallback works on Timers * Add setInterval and nextTick to domain test * domain: Make stack private
2012-04-06 23:26:18 +00:00
if (process.domain) timer.domain = process.domain;
repeat = ~~repeat;
if (repeat < 1 || repeat > TIMEOUT_MAX) {
repeat = 1; // schedule on next tick, follows browser behaviour
}
var args = Array.prototype.slice.call(arguments, 2);
timer.ontimeout = function() {
callback.apply(timer, args);
2010-10-26 19:52:31 +00:00
}
timer.start(repeat, repeat);
return timer;
};
2010-10-26 19:52:31 +00:00
2010-12-02 04:59:06 +00:00
exports.clearInterval = function(timer) {
if (timer instanceof Timer) {
timer.ontimeout = null;
timer.close();
}
};