Re: ACTION-245: Implementation of Media Fragments from Dailymotion

Le 14 déc. 2011 à 13:49, Raphaël Troncy a écrit :

> 2/ Partial implementation of Media Fragments Recipes in their server.
> Currently, Dailymotion has a partial implementation of the "Server mapped byte ranges" reciped described at http://www.w3.org/TR/media-frags-recipes/#processing-protocol-Server-mapped

To be more specific, we synthetize an entire new document based on the requested time-range. We solely rely on the MP4 container (and AVC/AAC
codecs) for Dailymotion (no support for OGG or Matroska containers),  and the resulting document is a valid self-contained playable MP4 file. So this
is not even what's described in section 2.2.2 "Server mapped byte ranges with corresponding binary data and codec setup data".

> For example, if you catch the requests made when putting in your browser this URL, http://www.dailymotion.com/video/xmslf5_la-chef-de-c-a-vous-chute-en-plein-direct_tv?start=37&end=46 you will see:
> 
> GET http://proxy-56.dailymotion.com/video/186/582/38285681_mp4_h264_aac_hq_1.mp4?auth=1323873600.62b73aa070711d60b88df1268d7ed7e2&start=37
> 
> which triggers the request:
> 
> Host	proxy-56.dailymotion.com
> User-Agent	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0.1) Gecko/20100101 Firefox/8.0.1
> Accept	text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
> Accept-Language	en,en-us;q=0.8,fr;q=0.5,fr-fr;q=0.3
> Accept-Encoding	gzip, deflate
> Accept-Charset	ISO-8859-1,utf-8;q=0.7,*;q=0.7
> Connection	keep-alive
> Cookie		...
> 
> and the following response (200 OK) from the server:
> 
> Date	Wed, 14 Dec 2011 12:40:00 GMT
> Server	Apache
> Accept-Ranges	bytes, seconds
> X-Accept-TimeURI	npt, smpte-24, smpte-24-drop, smpte-25, smpte-30, smpte-30-drop
> X-Edge-Version	1.7.3
> Etag	9037352b189c963eb973e5bb93540867
> Last-Modified	Tue, 06 Dec 2011 11:43:10 GMT
> Content-Length	4784581
> Connection	close
> Content-Type	video/mp4
> 
> Changes to be made to be compliant with our specification:
>  - A normal request is performed at the moment and a 200 OK answer is sent back because of the use of the query parameter. If the fragment would be used, then one could imagine doing a Range request with a 206 Partial Content response.
>  - The X-Accept-TimeURI header is used because Dailymotion has read http://www.w3.org/2008/WebVideo/Fragments/wiki/UA_Server_HTTP_Communication and http://lists.w3.org/Archives/Public/public-media-fragment/2009Apr/0075.html but this has been dropped since.
>  - The Content-Range and the Content-Range-Mapping headers are not yet provided in the answer but they could be added.

Cordialement,

-- 
Pierre-Yves Kerembellec | Senior IT Expert
Dailymotion | 49-51 rue Ganneron | 75018 Paris - France
Tel : +33 1 77 35 11 09 | Mobile : +33 6 08 91 46 15

Received on Wednesday, 14 December 2011 17:12:25 UTC