Non-blocking, temporal task sequencing.
temporal does NOT use
setInterval, however there is a cost for using "recursive"
setImmediate to create an extremely fast, async execution loop. CPU usage is expected to peak when using
temporal, because the internal ticker needs to execute as fast as possible and as many times per second as possible. It's this speed that allows
temporal to review the internal schedule for tasks to execute more than once per millisecond, which is needed to create preferential execution cycles for hardware programming.
temporal is for writing timing sensitive programs that are expected to be the primary process running on a given system, where the power source itself is tuned to accommodate that program specifically. Concrete examples include:
temporal is not good for sparse task scheduling.
npm install temporal
var temporal = ;temporal;// Wait 500 milliseconds, execute a tasktemporal;// Loop every n milliseconds, executing a task each timetemporal;// Queue a sequence of tasks: delay, delay// Each delay time is added to the prior delay times.temporal;// Queue a sequence of tasks: delay then loop// Each delay time is added to the prior delay times.temporal;
In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using grunt.
See LICENSE file.