- From: Raphaël Troncy <raphael.troncy@cwi.nl>
- Date: Wed, 19 May 2010 10:31:27 +0200
- To: Davy Van Deursen <davy.vandeursen@ugent.be>
- CC: 'Media Fragment' <public-media-fragment@w3.org>
Hi Davy, > - restructured section 5.2 in such a way that we don’t have 4 plain > recipes to resolve HTTP media fragments, but rather divided it in two > major parts: UA mapped byte ranges and server mapped byte ranges. In > case of server mapped byte ranges, there are then three possibilities: > server mapped byte ranges with corresponding binary data, server mapped > byte ranges with corresponding binary data and codec setup data, and > proxy cacheable server mapped byte ranges. > > - described the missing recipe where codec setup information is > requested by the UA. > > - removed the spatial dimension within the server mapped byte ranges > section. > > - added a motivation for not supporting the spatial dimension within > server mapped byte ranges. > > - tweaked some details in the examples throughout section 5.2. Great job, thanks a lot! We will discuss this re-structuring today in order to make sure everybody agrees! Cheers. Raphaël -- Raphaël Troncy EURECOM, Multimedia Communications Department 2229, route des Crêtes, 06560 Sophia Antipolis, France. e-mail: raphael.troncy@eurecom.fr & raphael.troncy@gmail.com Tel: +33 (0)4 - 9300 8242 Fax: +33 (0)4 - 9000 8200 Web: http://www.eurecom.fr/~troncy/
Received on Wednesday, 19 May 2010 08:33:04 UTC