W3C home > Mailing lists > Public > public-web-perf@w3.org > February 2018

Re: Is there any way to deal with streaming content?

From: Anton Nemtsev <newsilentimp@gmail.com>
Date: Tue, 27 Feb 2018 19:36:02 +0200
Message-ID: <CA+JO0fJn2m-SwUgd+UQSEY87+7SUzCqFP0gORD9QrAA2RCM-iA@mail.gmail.com>
To: Ilya Grigorik <igrigorik@google.com>
Cc: Patrick McManus <pmcmanus@mozilla.com>, public-web-perf <public-web-perf@w3.org>
Guys, sorry, but how I actually may send headers after body at all.
I try to google it, but no luck.
I use node.js server at the moment but will be happy to get any rtfm
or direction.

On Mon, Feb 26, 2018 at 6:32 PM, Ilya Grigorik <igrigorik@google.com> wrote:
> Yay! Great to hear. Do we have an ETA or bug to follow? Curious to test it
> out.
> On Mon, Feb 26, 2018 at 8:20 AM Patrick McManus <pmcmanus@mozilla.com>
> wrote:
>> firefox is doing support for server-timing in trailers. Its actually the
>> only trailer we will support. (so far.)
>> On Wed, Feb 21, 2018 at 11:20 PM, Ilya Grigorik <igrigorik@google.com>
>> wrote:
>>> Hi Anton. Yes, and no..
>>> Server-Timing is communicated via an HTTP header field that, per spec,
>>> can either be present in the initial set of response headers before the
>>> response body, or as a trailer after the response. As such, one could, in
>>> theory, deliver a Server-Timing trailer *after* the full response body has
>>> been streamed, annotating the individual chunks — note that you can't
>>> interleave this data with the response itself.
>>> The one extra wrinkle here is that trailer support is still lacking:
>>> Chrome does not support it (yet, at least), and afaik Mozilla implemented
>>> partial support but it's not wired up fully for Server-Timing.
>>> On Sun, Feb 18, 2018 at 10:46 PM, Anton Nemtsev <newsilentimp@gmail.com>
>>> wrote:
>>>> Hi,
>>>> am I right and there are no way to transfer server-timings if you stream
>>>> content?
>>>> For example when I use renderToNodeStream to render html on server side?
>>>> Regards.
Received on Tuesday, 27 February 2018 17:36:28 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 27 February 2018 17:36:29 UTC