Mercurial > hg > nginx-site

comparison xml/en/docs/http/ngx_http_mp4_module.xml @ 1096:f34be6b26447

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Corrected text formatting for ngx_http_mp4_module.
author Yaroslav Zhuravlev <yar@nginx.com>
date Tue, 04 Mar 2014 13:02:21 +0000
parents 379cb572a7ec
children 1fcf8c840dbe
comparison
equal deleted inserted replaced
1095:8a8cab5a131b 1096:f34be6b26447
43 </para> 43 </para>
44 44
45 <para> 45 <para>
46 To start playback, a player first needs to read metadata. 46 To start playback, a player first needs to read metadata.
47 This is done by sending a special request with the 47 This is done by sending a special request with the
48 <literal>start=0</literal> 48 <literal>start=0</literal> argument.
49 argument. Much of encoding software will insert the metadata at 49 Much of encoding software will insert the metadata at
50 the end of the file. This is bad for pseudo-streaming: 50 the end of the file.
51 This is bad for pseudo-streaming:
51 the metadata should be located at the beginning of the file, 52 the metadata should be located at the beginning of the file,
52 or else the entire file will have to be downloaded to 53 or else the entire file will have to be downloaded to
53 start playing. If a file is well-formed (with metadata at the 54 start playing.
55 If a file is well-formed (with metadata at the
54 beginning of a file), nginx just sends back the file contents. 56 beginning of a file), nginx just sends back the file contents.
55 Otherwise, it has to read the file and prepare a new stream so that 57 Otherwise, it has to read the file and prepare a new stream so that
56 the metadata comes before the media data. 58 the metadata comes before the media data.
57 This involves some CPU, memory, and disk I/O overhead, 59 This involves some CPU, memory, and disk I/O overhead,
58 so it is a good idea to 60 so it is a good idea to