- From: Joseph Berkovitz <joe@noteflight.com>
- Date: Wed, 16 Nov 2011 16:39:44 -0500
- To: public-audio@w3.org
Received on Wednesday, 16 November 2011 21:40:13 UTC
On Nov 16, 2011, at 4:08 PM, Jonathan Baudanza wrote: > On Wed, Nov 16, 2011 at 12:32 PM, Chris Rogers <crogers@google.com> wrote: > > Is this something which can be addressed by CORS? > > Yes, it is. Jussi pointed this out last night. Unfortunately, Amazon S3 doesn't support CORS headers, so I'll have to stick with the IFRAME hack for now. This is an issue with S3 though, not the Web Audio spec. > > > This isn't exactly the same as what Joe proposed, but we're looking at a solution which is somewhat better than setTimeout(): > https://bugs.webkit.org/show_bug.cgi?id=70061 > > > This looks perfect. By the way, this approach gets my thumbs up too. ...Joe
Received on Wednesday, 16 November 2011 21:40:13 UTC