[Webkit-unassigned] [Bug 84885] [Resource Timing] Implement buffer limits

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=84885





--- Comment #13 from James Simonsen <simonjam at chromium.org>  2012-10-12 11:56:21 PST ---
(In reply to comment #11)
> one exception is, what if a smaller buffer size is set when previous buffer size is not achieved yet?

Good example. Do you want to raise that on the list? I vote we fire the event once immediately in that case.

> an extreme scenario is buffer size is set to 0 before any append() happen, I prefer fire the event in this condition if that is not fired on every resource that arrives after full.

That's an interesting idea and is inline with what I initially proposed for Resource Timing (I hate this buffer). I think it should be brought up on the list though.

> in addition, resource timing[1] said, "While executing the onresourcetimingbufferfull callback, PerformanceResourceTiming will continue to be collected beyond the maximum limit of the resources allowed in the PerformanceResourceTiming interface until...", seems this statement intends to ensure no resource timing entry loss when buffer is full. has it been discussed in web perf group?

This line doesn't apply to us. WebKit is single threaded. We can't add another resource to the buffer while the event is firing.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.