[foms] Proposal: adaptive streaming using open codecs

Jeroen Wijering jeroen at longtailvideo.com
Wed Oct 20 03:14:28 PDT 2010

On Oct 20, 2010, at 3:38 AM, Silvia Pfeiffer wrote:

>>> It only needs reloading for a live stream. There is no other means for
>>> a live stream to find out about the new files on the server other than
>>> through the manifest.
>> I was talking about adding a JS api to the manifest so that you could tell
>> it instead of having to reload the file.  That way if you had a scheme
>> (increasing numbers in file names) you could do that with an algorithm
>> instead of having it in a file.
> Ah! Yeah, that makes sense - normally they all follow a pattern. But
> hmmm.... you'd still need to do a first request to the server, so
> you'd get the manifest first and find out all the file basenames. For
> static content I'm not sure why you'd need to further use such a JS
> api then. For live stuff - as Ben said... I think that would be very
> useful...

Having API access to the in-browser manifest (both create and modify) might indeed be interesting. I'll add a small proposal for that, and then push the doc live at the WhatWG wiki, so everybody can edit it.

- Jeroen

More information about the foms mailing list