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

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

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:29:54 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/143/24244502@github.com>
> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17795#5) by Chris Wilson on W3C Bugzilla. Thu, 19 Jul 2012 16:48:51 GMT

(In reply to [comment #5](#issuecomment-24244495))
> Depends on your point of view I guess. In this case I think the author would
> expect connect() to cause a change in the output, and it won't.

I guess I translate connect() as "make sure these nodes are connected".  I see the model you're describing, and it's consistent; I think we just need to choose the simplicity of the model (no identifiers) vs the utility of multiple connections between node i/o points.

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/143#issuecomment-24244502
Received on Wednesday, 11 September 2013 14:30:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:50:11 UTC