public-web-perf@w3.org from November 2014 by author

Aaron Heady (BING AVAILABILITY)

RE: communicating server timing data to the client.. Server Timing? (Monday, 10 November)
RE: communicating server timing data to the client.. Server Timing? (Monday, 10 November)

Anthony van der Hoorn

Support for access response headers (Monday, 24 November)

Ben Maurer

Re: communicating server timing data to the client.. Server Timing? (Saturday, 22 November)
Re: communicating server timing data to the client.. Server Timing? (Monday, 10 November)

Edmund Huber

Re: communicating server timing data to the client.. Server Timing? (Monday, 10 November)

Eli Perelman

Re: communicating server timing data to the client.. Server Timing? (Wednesday, 12 November)
Re: communicating server timing data to the client.. Server Timing? (Wednesday, 12 November)

Ilya Grigorik

Re: communicating server timing data to the client.. Server Timing? (Wednesday, 19 November)
spec updates: Perf Timeline, Nav Timing, Resource Timing (Thursday, 13 November)
Re: communicating server timing data to the client.. Server Timing? (Wednesday, 12 November)
Re: communicating server timing data to the client.. Server Timing? (Wednesday, 12 November)
[agenda] teleconf 2014-11-12 (Tuesday, 11 November)
Re: [whatwg] allow <link> in body + DOM position as a rendering hint (Tuesday, 11 November)
Re: communicating server timing data to the client.. Server Timing? (Tuesday, 11 November)
Re: communicating server timing data to the client.. Server Timing? (Monday, 10 November)
Re: communicating server timing data to the client.. Server Timing? (Monday, 10 November)
Re: communicating server timing data to the client.. Server Timing? (Friday, 7 November)
communicating server timing data to the client.. Server Timing? (Friday, 7 November)
[performance-timeline] async timeline + events (Friday, 7 November)
Re: Ready indicator (Thursday, 6 November)
Re: negotiated protocol in Navigation and Resource Timing (Wednesday, 5 November)
Re: [whatwg] allow <link> in body + DOM position as a rendering hint (Saturday, 1 November)

Jonathan Watt

[NavigationTiming2] How many 'navigation' entries are available? (Thursday, 27 November)
[NavigationTiming2] document.open() issues (Thursday, 27 November)

McCall, Mike

Re: communicating server timing data to the client.. Server Timing? (Monday, 10 November)

Nic Jansma

Re: add "networkDuration" to Resource Timing (Tuesday, 25 November)
Re: add "networkDuration" to Resource Timing (Tuesday, 25 November)

Nottingham, Mark

Re: communicating server timing data to the client.. Server Timing? (Monday, 24 November)

Patrick Meenan

Re: add "networkDuration" to Resource Timing (Wednesday, 26 November)
Re: communicating server timing data to the client.. Server Timing? (Monday, 24 November)

Peter Lepeska

Re: add "networkDuration" to Resource Timing (Wednesday, 26 November)

Philippe Le Hegaret

Re: [Page Visibility 2] Request for Comments (Tuesday, 4 November)

Ritesh Maheshwari

Re: communicating server timing data to the client.. Server Timing? (Saturday, 8 November)

Simon Pieters

Re: [whatwg] allow <link> in body + DOM position as a rendering hint (Saturday, 1 November)

Steve Souders

Re: add "networkDuration" to Resource Timing (Tuesday, 25 November)
add "networkDuration" to Resource Timing (Tuesday, 25 November)
Re: communicating server timing data to the client.. Server Timing? (Friday, 7 November)

Tobin Titus

[agenda] Web Performance WG Teleconference #141 Agenda 2014-11-19 (Tuesday, 18 November)
RE: [agenda] teleconf 2014-11-12 (Wednesday, 12 November)
RE: communicating server timing data to the client.. Server Timing? (Monday, 10 November)
RE: Ready indicator (Monday, 10 November)

Yoav Weiss

Re: add "networkDuration" to Resource Timing (Tuesday, 25 November)

Last message date: Thursday, 27 November 2014 19:45:28 UTC