W3C home > Mailing lists > Public > public-audio@w3.org > July to September 2012

[Bug 17795] Behavior of multiple connections to same node needs to be explicitly defined

From: <bugzilla@jessica.w3.org>
Date: Thu, 19 Jul 2012 15:24:50 +0000
Message-Id: <E1Srsaw-0001RL-G1@jessica.w3.org>
To: public-audio@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17795

--- Comment #2 from Chris Wilson <cwilso@gmail.com> 2012-07-19 15:24:50 UTC ---
If you allow multiple connections between two nodes*, then you'll have to
provide an identifier for that connection, and enable the disconnect() to take
that identifier (and require developers to hang on to that identifier).  Or,
said another way - if connect() always adds another connection, even if it
already exists, then what does disconnect() do, and how do you know when you
are really disconnected?  It seems like enabling multiple connections would
complexify the connect/disconnect part of the API significantly.

If there's a scenario for making multiple connections between two nodes*, I'm
open to hearing it; I just couldn't think of any.  I would presume it would
just effectively double the gain, which of course is easy to do in other ways.

*Technically, these should both read "the same input/output pair of two nodes."
 Of course you can make connections between different i/o pairs.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 19 July 2012 15:25:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 19 July 2012 15:25:06 GMT