Re: Requirements for Web audio APIs

On Mon, May 23, 2011 at 2:58 PM, Chris Rogers <crogers@google.com> wrote:

> I see it as more of an advantage than a problem.  In object-oriented
> design, it's often a good idea to separate out concepts into separate types
> of objects with "has-a" relationships instead of lumping together distinct
> and separate concepts into monolithic object classes.  As an example of two
> quite different types of objects I would look at HTMLMediaElement, a type
> which is very much concerned with network state and buffering as evident in
> its API.   And the AudioNode,  which deals with concepts very particular to
> audio, connections with processing nodes in a graph, etc.   So, I see it as
> an advantage to keep them separate.


The apparent redundancy is with AudioNode and Stream, not HTMLMediaElement.

Rob
-- 
"Now the Bereans were of more noble character than the Thessalonians, for
they received the message with great eagerness and examined the Scriptures
every day to see if what Paul said was true." [Acts 17:11]