The AudioNode interface doesn't allow one to discover its set of connected input and output AudioNodes (e.g. through readonly computed Array attributes like connectedInputNodes, connectedOutputNodes). This often requires a developer to separately track connection state in a way that feels unnecessarily complicated and is also error-prone.
Also, the inability to determine the set of connected nodes feels at odds with other web APIs in which modifications to an object's state can usually be read back.
This is related/equivalent to the recent discussion on the need for AudioContext introspection, for which there have been discussion on the group's list recently.
There have been other discussion on the list. Links TBA.
Per http://www.w3.org/2012/09/26-audio-minutes#item04 the group decided that this was a feature which we should not focus on for the time being.
No objection after close to 2 weeks. Closing.