We should add a processing model section similar to http://padenot.github.io/web-audio-api/#processing-model (currently an early draft by @padenot). Consider at least threads, message passing, event loops, asynchronous operations. I think we share much of the common ground with the Web Audio API processing model, and should reuse and adapt the model and terminology for this spec when more settled.
We should add a processing model section similar to http://padenot.github.io/web-audio-api/#processing-model (currently an early draft by @padenot). Consider at least threads, message passing, event loops, asynchronous operations. I think we share much of the common ground with the Web Audio API processing model, and should reuse and adapt the model and terminology for this spec when more settled.