I'm having trouble understanding exactly how process.nextTick
does its thing. I thought I understood, but I can't seem to replicate how I feel this should work:
var handler = function(req, res) {
res.writeHead(200, {'Content-type' : 'text/html'});
foo(function() {
console.log("bar");
});
console.log("received");
res.end("Hello, world!");
}
function foo(callback) {
var i = 0;
while(i<1000000000) i++;
process.nextTick(callback);
}
require('http').createServer(handler).listen(3000);
While foo
is looping, I'll send over several requests, assuming that handler
will be queued several times behind foo
with callback
being enqueued only when foo
is finished.
If I'm correct about how this works, I assume the outcome will look like this:
received
received
received
received
bar
bar
bar
bar
But it doesn't, it's just sequential:
received
bar
received
bar
received
bar
received
bar
I see that foo
is returning before executing callback
which is expected, but it seems that callback
is NEXT in line, rather than at the end of the queue, behind all of the requests coming in. Is that the way it works? Maybe I'm just not understanding how exactly the event queue in node works. And please don't point me here. Thanks.