User agents (eg. IPFS-aware web browser) could utilize hints passed in Server Timing headers to improve user experience by providing higher resolution feedback about the state of request.
Example
> GET /ipfs/QmFoo HTTP/1.1
> Host: ipfs.io
< HTTP/1.1 200 OK
< Server-Timing: miss, ds;dur=53, dht;dur=47.2, bitswap;dur=120
< Server-Timing: cache;dur=23.2
The Server Timing API allows you to pass request-specific timing data from your server to the browser via response headers
Potential uses
In IPFS context, it could be a way for HTTP Gateway to indicate how long it took to
/api/v0/call/ipfs/*request, namely:Improved debugging
As illustrated by @Gozala in https://github.com/ipfs-shipyard/ipfs-webui/pull/1534#issuecomment-652645285 I think bifrost team and other gateway providers could leverage it for debugging gateway performance when processing a specific request.
Improved UX in browser context
User agents (eg. IPFS-aware web browser) could utilize hints passed in Server Timing headers to improve user experience by providing higher resolution feedback about the state of request.
Example
References