[foms] Proposal: adaptive streaming using open codecs

Jeroen Wijering jeroen at longtailvideo.com
Wed Oct 20 03:59:11 PDT 2010

On Oct 19, 2010, at 9:46 PM, Benjamin M. Schwartz wrote:

>>> but also
>>> might be really useful if you don't want to have to keep reloading the
>>> manifest and can generate it from another source.
>> 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.
> As others have pointed out, there are other mechanisms.  Most notably, a
> naming scheme may easily be selected such that the names of all future
> chunks is known in advance.  (e.g. <filename>-<incrementing number>.webm)
> --Ben

A naming scheme might indeed be useful for basic cases;  this could be linked to the "Manifest API" Christopher talked about. With such an API, manifests would not be required. 

A naming scheme / API cannot be the only option though, since there'll be issues around such cases as:

* Load balancing (mid-stream failure of a server, redirection to the other)  
* Encoding issues (discontinuities in the chain/scheme)
* Dynamic insertion of unrelated chunks (e.g. for pre/mid/postroll advertising)

- Jeroen

More information about the foms mailing list