Re: Proposal for output device selection

In particular, the digital audio workstation type case - or any music app
that wants access to multiple hardware interfaces, like a DJ app that has a
cue output as well as a mains output - typically has to leave this up to
the user, since it's hard to semantically define the "roles" of different
devices (sometimes there's no semantic difference - I just have two
four-track interfaces, and I want to have eight tracks of output, etc.)


On Thu, Aug 15, 2013 at 4:18 PM, Martin Thomson <martin.thomson@gmail.com>wrote:

> On 15 August 2013 15:51, Robert O'Callahan <robert@ocallahan.org> wrote:
> > It's easy for the UA to make choices stick over time for the same
> > application. I just said that.
>
> You did, but that's not the same as having the application able to
> manage those choices over time.  The problem with having the UA do
> this is that it is often ignorant of application context.  It can even
> have difficulty identifying a specific application.  The same origin
> can host multiple applications, or the one application can appear on
> multiple origins.
>
> From an application developer perspective, I don't trust the UA to get
> this right.
>