W3C home > Mailing lists > Public > public-audio@w3.org > October to December 2012

[Bug 17417] Define a security model for requesting access to the MIDIAccess interface

From: <bugzilla@jessica.w3.org>
Date: Sat, 29 Dec 2012 01:24:25 +0000
To: public-audio@w3.org
Message-ID: <bug-17417-5429-Wgm4dyJIuJ@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17417

--- Comment #15 from Marcos Caceres <w3c@marcosc.com> ---
I've been trying to come up with a more incremental security model to address
the common use case of just getting access to system default ports without
needing to ask for permission (perfect for games sound effects) - while at the
same time incrementally increasing the security controls to allow users to
control what inputs and outputs are made available to an application (and also
handle the case of hot plugging and unplugging devices). FWIW, I don't think
the current security model handles this well (and may even break if the API
does eventually have to deal with people plugging and unplugging devices).

My extremely preliminary thoughts are captured in the link below:

https://gist.github.com/4384745

It would require some significant changes to the API (e.g., having a single
midi access point and doing away with the MIDIAccess object). 

As I now have a more or less functional reference implementation of the MIDI
API, I'll try to prototype a demo over the next week. However, if anyone wants
to help me hash out these ideas, that would be greatly appreciated.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Saturday, 29 December 2012 01:24:27 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:50:04 UTC