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

[Bug 19762] "connect" event not logically possible, and disconnect hard to implement

From: <bugzilla@jessica.w3.org>
Date: Wed, 31 Oct 2012 19:53:52 +0000
To: public-audio@w3.org
Message-ID: <bug-19762-5429-xhpVo7LVbI@http.www.w3.org/Bugs/Public/>

--- Comment #1 from Chris Wilson <cwilso@gmail.com> ---
Removed connect/disconnect events -
https://dvcs.w3.org/hg/audio/rev/46c470599a4b - for simplicity reasons in v1.

The current model for input and output ports is similar to the Windows MIDI
model, or the CoreMIDI model of Source and Destination iteration - NOT
CoreMIDI's "GetDevices" model, which includes offline devices.  (Windows does
not include a similar model.)

In order to add connect and disconnect events, we would need to:

1) define the lifecycle of a MIDIPort (actually, a MIDIInput or MIDIOutput) -
that is, state what happens when it goes offline and then comes back online, or
what happens if you ask for getInput and hand a reference to a port that has
gone offline;

2) have "connect" notifications fire on the MIDIAccess, so the developer would
know that a new device has come online; optionally (depending on answers above)
additionally fire that event on the MIDIPort itself.

3) "disconnect" should also fire on the MIDIAccess as well as any open
instances of the MIDIPort - that would help developers know to update, e.g., a
current "live list" of available MIDI ports.

4) Clearly state what happens when a reference to an offline MIDI port is
handed to getInput or getOutput.

In looking at all these issues, it seemed much better to simplify the model in
v1, and examine usage scenarios in the future.

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 31 October 2012 19:53:53 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:03:14 UTC