- From: Davy Van Deursen <davy.vandeursen@ugent.be>
- Date: Tue, 31 May 2011 15:33:19 +0200
- To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- CC: Media Fragment <public-media-fragment@w3.org>, Raphaël Troncy <raphael.troncy@eurecom.fr>
On 27/05/2011 11:43, Silvia Pfeiffer wrote:
> Hmm... I wonder if the server knows how to map the chapter to time and
> how to map time to byte ranges, why would it not immediately go from
> chapter to byte ranges?
Good question. I think we have the following two possibilities:
1) Redirect to a temporal fragment
GET /video.ogv HTTP/1.1
Range: chapter=chapter1
=>
HTTP/1.1 307 Temporary Redirect
Location: http://www.example.com/video.ogv#t=10,20
2) Serve bytes
GET /video.ogv HTTP/1.1
Range: chapter=chapter1
=>
HTTP/1.1 206 Partial Content
Content-Length: 3743
Content-Type: video/ogg
Content-Range: bytes 19147-22880/35614993
Content-Range-Mapping: { chapter chapter1 } = { bytes 19147-22880/35614993 }
You are right that, for the first case, the server needs to know the
mapping between chapters and time ranges; while in the second case it is
sufficient to have a mapping between chapters and byte ranges.
I think that we should recommend the second case, but nothing prevents a
server from following the first case.
Best regards,
Davy
--
Davy Van Deursen
Ghent University - IBBT
Department of Electronics and Information Systems - Multimedia Lab
URL: http://multimedialab.elis.ugent.be/dvdeurse
Received on Tuesday, 31 May 2011 13:33:23 UTC