W3C home > Mailing lists > Public > whatwg@whatwg.org > May 2011

[whatwg] JSON Playlist Format

From: Zachary Ozer <zach@longtailvideo.com>
Date: Thu, 5 May 2011 17:47:23 -0400
Message-ID: <BANLkTims9Q6cDMxxLHnwSMMFCie=iLGASA@mail.gmail.com>
The use case I'm thinking of is a blogging service that allows a
publisher to upload static files, but they cannot host executable code
like a proxy. They could include a <script> tag as part of their
content and use a third party JSONP
(http://en.wikipedia.org/wiki/JSONP) proxy to load their playlist.

Additionally, in older browsers (IE 6 & 7), I believe that
Access-Control-Allow-Origin headers aren't respected, so you'd never
be able to load XML cross domain, but you can load <script> tags.

Best,

Zach
--
Zachary Ozer
Developer, LongTail Video

w: longtailvideo.com ? e: zach at longtailvideo.com ? p: 212.244.0140 ?
f: 212.656.1335
JW Player? |? Bits on the Run? |? AdSolution



On Thu, May 5, 2011 at 12:08 PM, Nils Dagsson Moskopp
<nils at dieweltistgarnichtso.net> wrote:
> Zachary Ozer <zach at longtailvideo.com> schrieb am Thu, 5 May 2011
> 11:17:42 -0400:
>
>> We've been getting some traffic on our forums from users wondering
>> about JSON playlist formats. Specifically, because we aren't
>> supporting XML playlists in our player in HTML5 mode (setting the
>> Access-Control-Allow-Origin headers would be impossible for most of
>> our users), they're looking for a JavaScript-friendly way to
>> encapsulate their playlists.
>
> Which would also need CORS measures, or am I mistaken here?
>
>> A very cursory search turned up JSPF
>> (http://wiki.xiph.org/JSPF_Draft), but it appears to be in draft. Are
>> y'all aware of any other formats, either in draft or that have been
>> released? If no, any idea why no one's done it already?
>
> Probably because fallback to a proxy is way easier.
> Anything blocking the use of XSPF + pass-through proxies?
>
>
> Cheers,
> --
> Nils Dagsson Moskopp // erlehmann
> <http://dieweltistgarnichtso.net>
>
Received on Thursday, 5 May 2011 14:47:23 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:32 UTC