W3C home > Mailing lists > Public > public-audio@w3.org > April to June 2012

Re: Audio-ISSUE-104: Define a security model for requesting access to the MIDIAccess interface [MIDI API]

From: Jussi Kalliokoski <jussi.kalliokoski@gmail.com>
Date: Wed, 6 Jun 2012 17:11:49 +0300
Message-ID: <CAJhzemWkLQDyaDj6AV=3TkPNfs_4Mg5NMCbt5xZXpaq1WBhJBg@mail.gmail.com>
To: Audio Working Group <public-audio@w3.org>
This issue is now pending review per
https://dvcs.w3.org/hg/audio/rev/1ab2a972b9bc .

Cheers,
Jussi

P.S. It seems that I can't log in to our bugzilla. Do I need another login
than my W3C login?



On Wed, May 23, 2012 at 4:04 PM, Jussi Kalliokoski <
jussi.kalliokoski@gmail.com> wrote:

> Oh yeah, and here is the current Editor's Draft of the MIDI API
> Specification:
> https://dvcs.w3.org/hg/audio/raw-file/tip/midi/specification.html
>
>
> On Wed, May 23, 2012 at 3:53 PM, Audio Working Group Issue Tracker <
> sysbot+tracker@w3.org> wrote:
>
>> Audio-ISSUE-104: Define a security model for requesting access to the
>> MIDIAccess interface [MIDI API]
>>
>> http://www.w3.org/2011/audio/track/issues/104
>>
>> Raised by: Jussi Kalliokoski
>> On product: MIDI API
>>
>> The initial idea was that we'd use getUserMedia("midi") but this is
>> potentially confusing, as MIDIAccess is not a MediaStream. Maybe extend the
>> Navigator object with a similar function, such as
>> getMIDIAccess(successCallback, ?failureCallback)?
>>
>>
>>
>>
>
Received on Wednesday, 6 June 2012 14:12:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 6 June 2012 14:12:19 GMT