- From: Raphaël Troncy <raphael.troncy@eurecom.fr>
- Date: Thu, 04 Mar 2010 09:44:52 +0100
- To: Conrad Parker <conrad@metadecks.org>
- CC: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, Media Fragment <public-media-fragment@w3.org>
> the comma thing is not about "will be parsed to", but "is equivalent > to". So, an application could add the two headers in order: > > Content-Range: track audio > Content-Range: subtitle/653.791 My understanding was: this is invalid since we cannot have multiple Content-Range headers in a response. Now, you just verbatim in another email a paragraph from RFC2616 (Section 4.2 Message Headers) that seems to say that this is *valid*. So I'm now confused. Yves, could you please provide us a pointer that reference your original claim? 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 Thursday, 4 March 2010 08:46:03 UTC