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

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

From: <bugzilla@jessica.w3.org>
Date: Tue, 17 Jul 2012 18:40:12 +0000
To: public-audio@w3.org
Message-ID: <bug-17795-5429@http.www.w3.org/Bugs/Public/>

           Summary: Behavior of multiple connections to same node needs to
                    be explicitly defined
           Product: AudioWG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: minor
          Priority: P2
         Component: Web Audio API
        AssignedTo: crogers@google.com
        ReportedBy: cwilso@gmail.com
         QAContact: public-audio@w3.org

I noticed that the spec doesn't say what should happen when you multiply
connect() a node to another node, e.g.

nodeA.connect( nodeB );
nodeA.connect( nodeB );

Given the fan-out/sum-in model, it *could* be expected you could have multiple
independent connections.  The current Chrome behavior is that the second line
above is a no-op; I prefer this behavior, but it needs to be explicitly stated
in the AudioNode.connect() description.

Suggested text:

There can only be one connection between a given output of one specific node
and a given input of another specific node; multiple connections with the same
termini are ignored.  For example, 

nodeA.connect( nodeB );
nodeA.connect( nodeB );

will have the same effect as

nodeA.connect( nodeB );

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 Tuesday, 17 July 2012 18:40:14 UTC

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