W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > February 2012

[Bug 12399] <video> add bytesReceived, downloadTime, and networkWaitTime metrics

From: <bugzilla@jessica.w3.org>
Date: Fri, 10 Feb 2012 00:33:12 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1RveQK-0008AZ-O3@jessica.w3.org>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=12399

--- Comment #35 from Ian 'Hixie' Hickson <ian@hixie.ch> 2012-02-10 00:33:07 UTC ---
> > I'm saying there should be a network protocol that does this, yes. 
> 
> Oh. It couldn't all be just a network protocol, though, because a lot of the
> decisions have to be made on the client--only the client can know if it's able
> to play back a format well-enough.

Sure. The network protocol is nothing alone, it's just a way for the client to
communicate to the server. My point is that it should be done by the client and
the server, via a network protocol, not by a script running on the client.


> There's always going to be some browser somewhere that can't be updated (or
> which updates slowly--for example, most mobile browsers today) which the
> server-side will have to support.

There's always going to be some browser that doesn't support any of this. Or
that has a bug that means scripting doesn't run. Or indeed, that has scripting
disabled. Or any number of other weird states. I see nothing special about the
browser here as compared to script based on browser APIs.


> > I don't see why browser vendors and server vendors can't innovate also.
> 
> They can! And I agree that they should, and I agree that for most developers,
> having this built into the browser is absolutely the best solution. My point is
> that JS developers can push out new code from day to day, while it can take
> months or years for a new browser to have sufficient usage.

Modern browsers update continuously in a matter of weeks these days. It's just
as possible for a browser to improve faster than a site updates its code than
the other way around. In fact, since there are fewer browsers, it's more likely
that they'll be updated.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 10 February 2012 00:33:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 10 February 2012 00:33:14 GMT