Re: [web-audio-api] Behavior of multiple connections to same node needs to be explicitly defined (#143)

> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17795#1) by Chris Wilson on W3C Bugzilla. Thu, 19 Jul 2012 15:24:50 GMT

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.

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/143#issuecomment-24244468