Hi,
>What about deprecating the current filters and writing a new one that
>just adds the Server-Timing header?
+1 to deprecate the current ones.
Sven
On 04.02.20 21:48, Emond Papegaaij wrote:
Hi Martin,
I like the idea of the 'Server-Timing' headers. I didn't know this feature yet.
Hi Martin,
I like the idea of the 'Server-Timing' headers. I didn't know this feature yet.
However, these response filters also measure at the client side. The
time is recorded at the start of the head and again just after body. I
highly doubt this way of measuring gives a good indication of
On Tue, Feb 4, 2020 at 9:51 PM Martin Grigorov wrote:
> Hi,
>
> "window.defaultStatus" could be easily replaced with console.log()
>
> Those are usually used in DEV mode. I think it is fine to preserve them.
>
> As a last resort we can render the value as a response header.
> I remember
Hi,
"window.defaultStatus" could be easily replaced with console.log()
Those are usually used in DEV mode. I think it is fine to preserve them.
As a last resort we can render the value as a response header.
I remember Chromium has handling for some special response header and puts
its value in
Hi all,
Do you agree on this one? I see no use for these classes anymore, as
support for window.defaultStatus has been dropped by all major
browsers. They also log server time, but we have other and better
solutions for that.
Best regards,
Emond
On Tue, Feb 4, 2020 at 8:37 PM Emond Papegaaij
