HTTP-based streaming media protocol favorites
HTTP live streaming is still a draft of the Internet. Due to the limit of the HTTP protocol itself, for example, to specify Content-Length, it was previously thought that it could not be used as a streaming media protocol. After reading the draft, it is indeed a compromise, that is, dividing a media stream into one file and then using another file (suffixed with M3U, isn't it familiar? Listen to the opened file dialog box) to specify the file to be downloaded by the client and then the file to be downloaded.
View plaincopy to clipboardprint?
# Extm3u
# EXT-X-MEDIA-SEQUENCE: 0
# EXT-X-TARGETDURATION: 10
# Extinf: 10,
Http://media.example.com/segment1.ts
# Extinf: 10,
Http://media.example.com/segment2.ts
# Extinf: 10,
Http://media.example.com/segment3.ts
# EXT-X-ENDLIST
The above is a simple M3U File with three parts specified. According to the document, if you do not specify # EXT-X-ENDLIST, then the player will check this file every other time is updated, very troublesome, there is wood?
Probably it is like this, detailed things can see the RFC draft, http://tools.ietf.org/html/draft-pantos-http-live-streaming-06
Apple also provides a document at: http://disanji.net/iOS_Doc/#documentation/NetworkingInternet/Conceptual/StreamingMediaGuide/HTTPStreamingArchitecture/HTTPStreamingArchitecture.html#//apple_ref/doc/uid/TP40008332-CH101-SW2
This is probably the case.