The Hard Parts of Servers & Node.js Priority of Queue Execution
Transcript from the "Priority of Queue Execution" Lesson
[00:00:20] Hold each deferred, I call these deferred functions that we didn't run ourselves at, are gonna be autorun later, they're deferred, delayed, autorun later, in one of the tasks, jeez, when the node background API. These are actually, these C++ features, they're technically known as APIs. Interface is a posh word for, any functionality that's not in my language, but not in my world, but in someone else's.
[00:00:44] I interface with it. When any of the background nodes in C++ features complete this autorun function don't autorun them. Queue them up to be autorunned, autoran sorry. Autorun. Add the function to the call stack, in other words, execute the function, add it to the call stack, we do this with each of them.
[00:01:46] That function goes in the micro-task cube, but there's two of those. That one goes in B. The number one process of all that we don't even use is process.netFix, any function you pass there. That goes in to the very, very first queue. There we go people. Those are all the rules of node.