W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2014

[Bug 26917] New: For any chunk, progress event should be fired at least in 50ms since the arrival of the chunk

From: <bugzilla@jessica.w3.org>
Date: Mon, 29 Sep 2014 07:24:46 +0000
To: public-webapps@w3.org
Message-ID: <bug-26917-2927@http.www.w3.org/Bugs/Public/>

            Bug ID: 26917
           Summary: For any chunk, progress event should be fired at least
                    in 50ms since the arrival of the chunk
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XHR
          Assignee: annevk@annevk.nl
          Reporter: tyoshino@google.com
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org


Now the throttle (interval 50ms) is back to XHR spec again.

The new text says that "process response body" call made in 50ms since the last
"process response body" call will be no-op. Right?

Please imagine situation where two chunks come at time n and n + (1 ms), and
then the connection becomes idle. Based on the new text, we fire progress event
for the first chunk, but do nothing for the second since we'll enter idle

Blink fires a progress event after 50ms passes since the last progress event
firing if any chunk has arrived after the chunk which triggered the last
progress event. This ensures that for any chunk at least one progress event
will be fired for the chunk at least in 50ms since the chunk arrives.

I think this behavior is reasonable. What do you think?

You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 29 September 2014 07:24:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:27 UTC