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

[Bug 20506] New: Do we need MIDIOutput and MIDIInput?

From: <bugzilla@jessica.w3.org>
Date: Mon, 24 Dec 2012 08:17:43 +0000
To: public-audio@w3.org
Message-ID: <bug-20506-5429@http.www.w3.org/Bugs/Public/>

            Bug ID: 20506
           Summary: Do we need MIDIOutput and MIDIInput?
    Classification: Unclassified
           Product: AudioWG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: MIDI API
          Assignee: dave.null@w3.org
          Reporter: w3c@marcosc.com
        QA Contact: public-audio@w3.org

I'm wondering if we really need MIDIOutput and MIDinput to extend MIDIPort. It
seems like a bit of overkill to have to add two more additional interfaces to
the platform when all that is being added is "onmessage" and on "send()" by
each interface respectively. Additionally, the "type" attribute of MIDIPort is
already restricted to "input" or "output", hence it feels redundant to have a
whole new interface to determine the type of an object (which is already part
of the base class).

I recommend just folding MIDIPOutput and MIDIIntput back onto MIDIPort. An port
of type input simply does noting when send() is invoked, and MIDIPort of type
output does not receive message events.

Is there a particular use case I'm missing that is not already covered?

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 24 December 2012 08:17:44 UTC

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