Re: Raw data API - 5 - misc notes

> Relationship to workers and processes
> Note - not part of this proposal, but part of context:
> 
> Processing of real-time data needs to be performed real-time. Living on the browser main thread makes this impossible, and even living inside the renderer task makes it hard.
> We have to define means of exchanging MediaStreamTracks, RTPSenders and RTPReceivers between processes as part of making this type of thing performant.

For the use case I’ve been thinking about (doing computer vision for augmented reality on video from camera(s) on an AR or VR display of some form), running a worker is definitely desirable, when possible.  Computer vision code is very likely going to be implemented in a combination of WASM and GPU code:  feeding frames to WASM in a Worker is clean and simple, AS LONG as the timestamps are aligned with the timestamps in the rendering thread, so that we can align the results of the computer vision with the underlying AR/VR platform tracking and rendering data back in the main thread.

For doing work in the GPU, I’m not clear on the restrictions that might exist in accessing and running code in the GPU in a worker.