runKitePlayerWorker

The worker's side of KitePlayerWorker (#100). The worker binary's main calls this and returns; the worker then lives on the messages the page sends it.

It answers the page's first message by loading the codec module and building the player, with the canvas and the audio port that came beside that message. From then on it runs each call and replies to it once, applies each control and reports a refused one as a warning, and it sends the page the player's state, progress, statistics and events as they change.

Network addresses are read with synchronous range requests, which a worker may make, so an http, https or blob item plays here although the page's own player cannot open one.