Re: Adding Web Audio API Spec to W3C Repository

Hey Robert,

HTML5 Appcache offline caching sounds good, if this is defining that audio and video data is to be cached in an offline cache.

The HTML audio element would certainly be enough to meet our current demands. Implementations are broken, incomplete or perform too bad. We have yet to discover a single browser without audio issues.

Von: Robert O'Callahan <<>>
Antworten an: "<>" <<>>
Datum: Tue, 14 Jun 2011 04:22:15 -0700
An: Paul Bakaus <<>>
Cc: Doug Schepers <<>>, "<>" <<>>, Francois Daoust <<>>, Philippe Le Hegaret <<>>, "Michael(tm) Smith" <<>>, Dan Burnett <<>>, Dominique Hazael-Massieux <<>>, Tobie Langel <<>>, Christoph Martens <<>>
Betreff: Re: Adding Web Audio API Spec to W3C Repository

On Tue, Jun 14, 2011 at 9:39 PM, Paul Bakaus <<>> wrote:
Our focus is very much real world problems right now - we want to be able
to play, pause, stop and cache sounds. That's all for now - we'd be super
super happy if we'd have this today but we don't. I'm letting Chris chime
in on future sound specs, but to me, it's very clear we need tighter
control on device dependent implementations - I.e., a explicit section on
media caching ("This spec is only 100% implemented when audio media is
properly cached in cache manifests").

You mean the HTML5 Appcache offline caching?

It sounds like the HTML audio element would be enough for your needs. Is it? Are the implementations adequate?

"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]

Received on Tuesday, 14 June 2011 14:51:52 UTC