Initial resource timing integration.

Created a "fetch timing info" struct to hold the bookkeeping
necessary for resource timing.

Populated it with some of the required values, leaving some of
them for later patches as this is a big undertaking.

See w3c/resource-timing#252

Author: noamr

fetch.bs

@@ -175,8 +175,34 @@ lt="authentication entry">authentication entries</a> (for HTTP authentication).
 
  <dt><dfn for="fetch params">task destination</dfn> (default null)
  <dd>Null, a <a for=/>global object</a>, or a <a for=/>parallel queue</a>.
+ <dt><dfn for="fetch params">timing info</dfn>
+ <dd>A <a for=/>fetch timing info</a>.
 </dl>
 
+<p>A <dfn>fetch timing info</dfn> is a <a for=/>struct</a> used to maintain timing information
+later required by the resource timing and navigation timiing specs. It has the following <a for=struct>items</a>:
+<dl>
+  <dt><dfn for="fetch timing info">redirect start time</dfn> (default zero)
+  <dt><dfn for="fetch timing info">redirect end time</dfn> (default zero)
+  <dt><dfn for="fetch timing info">fetch start time</dfn> (default zero)
+  <dt><dfn for="fetch timing info">response start time</dfn> (default zero)
+  <dt><dfn for="fetch timing info">response end time</dfn> (default zero)
+  <dt><dfn for="fetch timing info">alpn negotiated protocol</dfn> (default null)
+  <dd>Null or a string.
+
+  <dt><dfn for="fetch timing info">worker start time</dfn> (default zero)
+  <dt><dfn for="fetch timing info">domain lookup start time</dfn> (default zero)
+  <dt><dfn for="fetch timing info">domain lookup end time</dfn> (default zero)
+  <dt><dfn for="fetch timing info">connection start time</dfn> (default zero)
+  <dt><dfn for="fetch timing info">connection end time</dfn> (default zero)
+  <dt><dfn for="fetch timing info">secure connection start time</dfn> (default zero)
+  <dt><dfn for="fetch timing info">request start time</dfn> (default zero)
+  <dt><dfn for="fetch timing info">transfer size</dfn> (default zero)
+  <dt><dfn for="fetch timing info">encoded body size</dfn> (default zero)
+  <dt><dfn for="fetch timing info">decoded body size</dfn> (default zero)
+</dl>
+
+
 <p>To <dfn>queue a fetch task</dfn>, given an algorithm <var>algorithm</var>, a
 <a for=/>global object</a> or a <a for=/>parallel queue</a> <var>taskDestination</var>, run these
 steps:
@@ -1020,8 +1046,9 @@ worked on in <a href=https://github.com/whatwg/fetch/issues/1156>issue #1156</a>
 
 <p>To <dfn export for=body>incrementally read</dfn> a <a for=/>body</a> <var>body</var>, given an
 algorithm <var>processBodyChunk</var>, an algorithm <var>processEndOfBody</var>, an algorithm
-<var>processBodyError</var>, and an optional null, <a for=/>parallel queue</a>, or
-<a for=/>global object</a> <var>taskDestination</var> (default null), run these steps.
+<var>processBodyError</var>, an optional null, <a for=/>parallel queue</a>, or
+<a for=/>global object</a> <var>taskDestination</var> (default null), and an optional 
+<a for=/>fetch timing info</a> <var>timingInfo</var> or null (default null), run these steps.
 <var>processBodyChunk</var> must be an algorithm accepting a <a for=/>byte sequence</a>.
 <var>processEndOfBody</var> must be an algorithm accepting no arguments. <var>processBodyError</var>
 must be an algorithm accepting an exception.
@@ -1037,14 +1064,15 @@ must be an algorithm accepting an exception.
   <p class=note>This operation will not throw an exception.
 
  <li><p>Perform the <a>incrementally-read loop</a> given <var>reader</var>,
- <var>taskDestination</var>, <var>processBodyChunk</var>, <var>processEndOfBody</var>, and
- <var>processBodyError</var>.
+ <var>taskDestination</var>, <var>processBodyChunk</var>, <var>processEndOfBody</var>,
+ <var>processBodyError</var> and <var>timingInfo</var>.
 </ol>
 
 <p>To perform the <dfn>incrementally-read loop</dfn>, given a {{ReadableStreamDefaultReader}} object
 <var>reader</var>, <a for=/>parallel queue</a> or <a for=/>global object</a>
 <var>taskDestination</var>, algorithm <var>processBodyChunk</var>, algorithm
-<var>processEndOfBody</var>, and algorithm <var>processBodyError</var>:
+<var>processEndOfBody</var>, algorithm <var>processBodyError</var>, and an optional 
+<a for=/>fetch timing info</a> <var>timingInfo</var> or null (default null):
 
 <ol>
  <li>
@@ -1055,6 +1083,9 @@ must be an algorithm accepting an exception.
    <dd>
     <ol>
      <li><p>Let <var>continueAlgorithm</var> be null.
+     <li><p>If <var>timingInfo</var> is not null, and <var>timingInfo</var>'s
+     <a for="fetch timing info">response start time</a> is not zero, set <var>timingInfo</var>'s
+     <a for="fetch timing info">response start time</a> to the result of calling <a for=/>current time</a>.
 
      <li><p>If <var>chunk</var> is not a {{Uint8Array}} object, then set
      <var>continueAlgorithm</var> to this step: run <var>processBodyError</var> given a
@@ -1088,8 +1119,12 @@ must be an algorithm accepting an exception.
     </ol>
 
    <dt><a for="read request">close steps</a>
-   <dd><ol><li><p><a>Queue a fetch task</a> given <var>processEndOfBody</var> and
-   <var>taskDestination</var>.</ol>
+   <dd><ol>
+    <li><p><a>Queue a fetch task</a> given <var>processEndOfBody</var> and
+      <var>taskDestination</var>.
+    <li><p>If <var>timingInfo</var> is not null, set <var>timingInfo</var>'s
+     <a for="fetch timing info">response end time</a> to the result of calling <a for=/>current time</a>.
+   </ol>
 
    <dt><a for="read request">error steps</a>, given <var>e</var>
    <dd><ol><li><p><a>Queue a fetch task</a> to run <var>processBodyError</var> given <var>e</var>,
@@ -1136,6 +1171,9 @@ null), run these steps. <var>processBody</var> must be an algorithm accepting a
  <var>reader</var>.
 </ol>
 
+   <p class=XXX>TODO: set <a for="fetch timing info">response start time</a> and <a for="fetch timing info">response end time</a>
+   values for full reads. See <a href="https://github.com/w3c/resource-timing/issues/252">Issue 252</a>.
+
 <hr>
 
 <p>To <dfn export>handle content codings</dfn> given <var>codings</var> and <var>bytes</var>, run
@@ -1902,7 +1940,6 @@ initially unset.
 allowed on the resource fetched by looking at the flag of the response returned. Because the flag on
 the response of a redirect has to be set if it was set for previous responses in the redirect chain,
 this is also tracked internally using the request's <a for=request>timing allow failed flag</a>.
-
 <hr>
 
 <p>A <a for=/>response</a> whose
@@ -2139,10 +2176,20 @@ identified by a <b>key</b> (a <a>network partition key</a>), an <b>origin</b> (a
     <var>origin</var>. [[!HTTP]] [[!HTTP-SEMANTICS]] [[!HTTP-COND]] [[!HTTP-CACHING]] [[!HTTP-AUTH]]
     [[!TLS]]
 
+
     <p>If <var>credentials</var> is false, then do <em>not</em> send a TLS client certificate.
 
     <p>If establishing a connection does not succeed (e.g., a DNS, TCP, or TLS error), then return
     failure.
+
+     <p class=XXX>TODO: set <a for="fetch timing info">alpn negotiated protocol</a>, 
+     <a for="fetch timing info">connection start time</a>, 
+     <a for="fetch timing info">connection end time</a>, 
+     <a for="fetch timing info">domain lookup start time</a>, 
+     <a for="fetch timing info">domain lookup end time</a>, 
+     <a for="fetch timing info">request start time</a>, 
+     and <a for="fetch timing info">secure connection start time</a> values here.
+     See <a href="https://github.com/w3c/resource-timing/issues/252">Issue 252</a>.
   </ol>
 
  <li>
@@ -3272,6 +3319,7 @@ the request.
 
  <li><p>Let <var>fetchParams</var> be a new <a for=/>fetch params</a> whose
  <a for="fetch params">request</a> is <var>request</var>,
+ <a for="fetch params">timing info</a> is a new <a for=/>fetch timing info</a>,
  <a for="fetch params">process request body</a> is <var>processRequestBody</var>,
  <a for="fetch params">process request end-of-body</a> is <var>processRequestEndOfBody</var>,
  <a for="fetch params">process response</a> is <var>processResponse</var>,
@@ -3348,6 +3396,8 @@ the request.
  <li><p>Run <a>main fetch</a> given <var>fetchParams</var>.
 </ol>
 
+<h3 id="sec-current-time">Current Time</h3>
+The <dfn>current time</dfn> is the present time given the <a for=/>global monotonic clock</a>.
 
 <h3 id=main-fetch>Main fetch</h3>
 
@@ -3360,6 +3410,9 @@ steps:
 
  <li><p>Let <var>response</var> be null.
 
+ <li><p>Set <var>fetchParams</var>'s <a for="fetch params">timing info</a>'s <a for="fetch timing info">fetch start time</a>
+ to the result of running <a for=/>current time</a>.
+
  <li><p>If <var>request</var>'s <a>local-URLs-only flag</a> is set and <var>request</var>'s
  <a for=request>current URL</a> is not <a lt="is local">local</a>, then set <var>response</var> to a
  <a>network error</a>.
@@ -3684,8 +3737,7 @@ steps:
 
  <li><p>Wait for either <var>response</var>'s <a for=response>body</a> to be null, or
  <var>response</var>'s <a for=response>body</a>'s <a for=body>stream</a> to be
- <a for=ReadableStream>closed</a> or <a for=ReadableStream>errored</a>, and then set
- <var>request</var>'s <a>done flag</a>.
+ <a for=ReadableStream>closed</a> or <a for=ReadableStream>errored</a>, and set <var>request</var>'s <a>done flag</a>.
  <!-- This is really bad and needs to be handled differently at some point. -->
 </ol>
 
@@ -3812,6 +3864,8 @@ these steps:
 
  <li><p>Let <var>actualResponse</var> be null.
 
+ <li><p>Let <var>timingInfo</var> be <var>fetchParams</var>'s <a for="fetch params">timing info</a>
+
  <li>
   <p>If <var>request</var>'s <a>service-workers mode</a> is "<code>all</code>", then:
 
@@ -3821,6 +3875,8 @@ these steps:
 
    <li><p>Set <var>response</var> to the result of invoking <a for=/>handle fetch</a> for
    <var>requestForServiceWorker</var>. [[!HTML]] [[!SW]]
+   <p class=XXX>TODO: set <a for="fetch timing info">worker start time</a> value.
+   See <a href="https://github.com/w3c/resource-timing/issues/252">Issue 252</a>.
 
    <li>
     <p>If <var>response</var> is not null, then:
@@ -3952,8 +4008,9 @@ these steps:
      <a for="filtered response">internal response</a> is <var>actualResponse</var>.
 
      <dt>"<code>follow</code>"
-     <dd><p>Set <var>response</var> to the result of running <a>HTTP-redirect fetch</a> given
-     <var>fetchParams</var> and <var>response</var>.
+     <dd><p>Set <var>timingInfo</var>'s <a for="fetch timing info">redirect start time</a> to 
+      <var>timingInfo</var>'s <a for="fetch timing info">fetch start time</a>, and set <var>response</var> to
+      the result of running <a>HTTP-redirect fetch</a> given <var>fetchParams</var> and <var>response</var>.
     </dl>
     <!-- not resetting actualResponse since it's no longer used anyway -->
   </ol>
@@ -4043,6 +4100,9 @@ run these steps:
   <p class="note no-backref"><var>request</var>'s <a for=request>body</a>'s <a for=body>source</a>'s
   nullity has already been checked.
 
+ <li><p>Set <var>fetchParams</var>'s <a for="fetch params">timing info</a>'s <a for="fetch timing info">redirect end time</a>
+ to the result of runnning <a for=/>current time</a>.
+
  <li><p><a for=list>Append</a> <var>locationURL</var> to <var>request</var>'s
  <a for=request>URL list</a>.
 
@@ -4720,8 +4780,9 @@ these steps:
         </ol>
 
        <li><p><a for=body>Incrementally read</a> <var>request</var>'s <a for=request>body</a> given
-       <var>processBodyChunk</var>, <var>processEndOfBody</var>, <var>processBodyError</var>, and
-       <var>fetchParams</var>'s <a for="fetch params">task destination</a>.
+       <var>processBodyChunk</var>, <var>processEndOfBody</var>, <var>processBodyError</var>,
+       <var>fetchParams</var>'s <a for="fetch params">task destination</a>, and
+       <var>fetchParams</var>'s <a for="fetch params">timing info</a>.
        <!-- This obtains a reader in parallel, but it's mostly fine since we already proxied the
             input stream as part of the Request constructor. -->
       </ol>
@@ -4820,17 +4881,30 @@ these steps:
 
         <ol>
          <li><p>Let <var>bytes</var> be the transmitted bytes.
+         <li><p>Let <var>timingInfo</var> be the <var>fetchParams</var>'s <a for="fetch params">timing info</a>.
 
          <li><p>Let <var>codings</var> be the result of <a>extracting header list values</a> given
          `<code>Content-Encoding</code>` and <var>response</var>'s <a for=response>header list</a>.
 
+         <li><p>Set <var>timingInfo</var>'s <a for="fetch timing info">transfer size</a> to the result of
+         adding <var>timingInfo</var>'s <a for="fetch timing info">transfer size</a> and <var>bytes</var>.
+        
+         <p class=XXX>TODO: <a for="fetch timing info">transfer size</a> should also include the total size of the headers.
+         See <a href="https://github.com/w3c/resource-timing/issues/252">Issue 252</a>.
+
+         <li><p>Set <var>timingInfo</var>'s <a for="fetch timing info">encoded body size</a> to the result of
+         adding <var>timingInfo</var>'s <a for="fetch timing info">encoded body size</a> and <var>bytes</var>.
+
          <li>
           <p>Set <var>bytes</var> to the result of <a lt="handle content codings">handling content
           codings</a> given <var>codings</var> and <var>bytes</var>.
 
           <p class="note no-backref">This makes the `<code>Content-Length</code>` <a for=/>header</a>
           unreliable to the extent that it was reliable to begin with.
 
+         <li><p>Set <var>timingInfo</var>'s <a for="fetch timing info">decoded body size</a> to the result of
+         adding <var>timingInfo</var>'s <a for="fetch timing info">decoded body size</a> and <var>bytes</var>.
+
          <li><p>If <var>bytes</var> is failure, then <a lt=terminated for=fetch>terminate</a> the
          ongoing fetch.