- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Thu, 21 May 2009 19:51:58 +1000
- To: Raphaël Troncy <Raphael.Troncy@cwi.nl>
- Cc: Media Fragment <public-media-fragment@w3.org>
Tracker, this is ISSUE-10. There is another test case to consider, which I forgot yesterday: we have to take into account whether a time frame is within the duration of a file or outside. So, for #t=x,y request, with x,y integer and y>x , we have several cases: * x,y <= duration which is the good case, * x,y > duration, in which case it should be "416 Requested Range Not Satisfiable" IMHO (same as the other problem cases) * x,y with x < duration and y > duration, in which case I am not really sure what to return (probably 206). Cheers, Silvia. 2009/5/21 Raphaël Troncy <Raphael.Troncy@cwi.nl>: > Tracker, this is ISSUE-10. > >> I had a side discussion about the correct codes to use for some of the >> test cases. >> http://www.w3.org/2008/WebVideo/Fragments/wiki/TestCasesDiscussion >> >> I still think that "416 Requested Range Not Satisfiable" is the >> correct response to #t=0,0 or to #t=30,0 type requests. There is no >> fragment (or byte range) there at those URIs and therefore it is a >> client error. > > I agree with all your suggestions, and I think Michael is about to modify > http://www.w3.org/2008/WebVideo/Fragments/wiki/TestCases accordingly. > Michael, regarding the problem of adding the status code response for each > test case, does it mean you need to modify the vocab controlling the test > cases output? > Cheers. > > Raphaël > > -- > Raphaël Troncy > CWI (Centre for Mathematics and Computer Science), > Science Park 123, 1098 XG Amsterdam, The Netherlands > e-mail: raphael.troncy@cwi.nl & raphael.troncy@gmail.com > Tel: +31 (0)20 - 592 4093 > Fax: +31 (0)20 - 592 4312 > Web: http://www.cwi.nl/~troncy/ >
Received on Thursday, 21 May 2009 09:53:02 UTC