W3C home > Mailing lists > Public > public-webapi@w3.org > February 2007

Re: Progress event spec

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Fri, 02 Feb 2007 12:30:59 +0100
To: jean-claude.dufourd@streamezzo.com
Cc: Web API public <public-webapi@w3.org>
Message-ID: <ql76s2lbb9siho4aa7or44gd4elsj30v3e@hive.bjoern.hoehrmann.de>

* Jean-Claude Dufourd wrote:
>> Take http://www.w3.org/TR/SVG11/struct.html#uriReferenceDefinition as
>> an example, "URI references that directly or indirectly reference
>> themselves are treated as invalid circular references. ... An invalid
>> circular URI reference represents an error." The empty string treated
>> as URI reference is always a same-document reference and therefore in-
>> herently circular.
>
>JCD: From SVGT12 CR: 

Yes, that document specifies many weird things. Note that it does not
discuss whether implementations must or must not generate a load event
in this case, there are a few vague hints in either direction at best.

>JCD: the difference is: for any non-live video stream, you know the 
>length at the beginning, so would provide a length in all progress 
>events. For a live recording, you have no idea.

Actually you don't, there are many video formats that do not include the
total length in the header and the transport protocol might not provide
such information either, for example HTTP with chunked transfer encoding
might be used. Anyway, as I understood you, you want to know about the
end of the recording, not about the progress. So if progress information
is the only difference, then there is none that affects your problem.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de
68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Friday, 2 February 2007 11:37:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:57 GMT