3 ms·
> remove anything higher than seconds resolution of time unless the program actually demonstrates a need for it As someone working with Web Audio, I wonder if
by lioeters 7y ago
> remove anything higher than seconds resolution of time unless the program actually demonstrates a need for it
As someone working with Web Audio, I wonder if it's even possible to tell if a program "legitimately" needs milli/microseconds timing precision? Typically it'd be running on its own worker/audiolet(?) thread, but I imagine it could be exploited for some nefarious purpose.
Edit: I realized the talk is about WASM on the server, but, who knows, maybe in the future it could also involve audio that needs high-precision timers.
- xena 7y agoYeah, my thought there is make resolution of timers a dependent capability. My ultimate goal is to let users be able to say "no, $APP doesn't need more than second resolution of timers", and if the user is wrong the app just has to deal with it.
- lioeters 7y agoThat makes sense. In browsers there are already restrictions around audio/video autoplay, as an example, and an application needs logic around waiting for user permission. So I can imagine something similar, where the default timer could be coarse, and high-resolution timing would require elevated privileges. Anyway, thank you for the notes/slides about WebAssembly on the server, fascinating stuff with a bright future!