On Aug 14, 2008, at 1:34 PM, Reto Bachmann-Gmür wrote:
> Not sure about the best default value, but knowing about quality
> differences in producible content is necessary to deliver the
> optimal available content. The best format is the one where the
> product of server-side and client-side q-value is highest.
>
That may be the case for some applications but I don't think baking-in
something along those lines is the right thing to do.
> Example:
> The class Song encapsulates an ogg-vorbis stream, on the server
> there are producers for following content-types:
>
> - application/ogg;q=1
> - audio/x-ms-wma;q=.8
> - audio/mpeg;q=.9
>
> As our audio object encapsulates ogg-vorbis data, so application/ogg
> can be produced without quality loss, but producing mp3 reduces
> quality by 10% and wma 20%.
>
>
> The client sends a request with the following header:
>
> Accept: audio/x-ms-wma, audio/mpeg;q=.9, application/ogg;q=.7
>
Given the above I think its perfectly acceptable for the framework to
automatically select audio/x-ms-wma. An alternative selection can be
implemented within an application if desired.
Marc.
> Delivering audio/mpeg the user can listen to the song with a 19%
> mark-down in quality and that's the best quality she can get.
>
> Reto
>
---
Marc Hadley <marc.hadley at sun.com>
CTO Office, Sun Microsystems.