This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 8459 - "For instance, a user agent might wait 500ms or 512 bytes, whichever came first." -- IMO this is a bad example, over a satellite link the typical RTT might be 600-1500ms. Or is the assumption that the counting starts after the first packet of data is rece
Summary: "For instance, a user agent might wait 500ms or 512 bytes, whichever came fir...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-08 15:09 UTC by contributor
Modified: 2010-10-04 14:29 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2009-12-08 15:09:26 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#determining-the-character-encoding

Comment:
"For instance, a user agent might wait 500ms or 512 bytes, whichever came
first." -- IMO this is a bad example, over a satellite link the typical RTT
might be 600-1500ms. Or is the assumption that the counting starts after the
first packet of data is received?

Posted from: 72.171.0.145
Comment 1 Ian 'Hixie' Hickson 2010-01-06 05:39:34 UTC 
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: Certainly there are environments where 500ms is excessively short (satellite links aren't the half of it; consider mobile phone networks!). There are also environments where it's too long (e.g. when I'm on a network backbone link, there really is no reason to wait more than 100ms for anything that's being served from the same coast). It is just an example, intended to illustrate possible criteria that a user agent could use. User agents are expected (as is implied by that paragraph) to pick whatever is best for their users.