Stats API Requirements about webtransport HOT 6 CLOSED

Step 3 in getStats still says "If the URL scheme associated with transport is not quic-transport, reject p with NotSupportedError and return p." - even though we don't support quic-transport anymore, which means this method always rejects now.

So we need to discuss what to do with this API.

from webtransport.

So we need to discuss what to do with this API.

To be discussed in #206.

from webtransport.

Reopening, to discuss the stats API shape separately.

from webtransport.

What is the summary of discussion so far? is there a link to an email archive or PR?

from webtransport.

@vr000m - Meeting notes are stored on the wiki at - https://www.w3.org/wiki/WebTransport . Click to the particular meeting you are interested in. We have full recordings and transcripts linked with each meeting archive.

from webtransport.

I think we have general idea of shape now, with connection-level and aggregate stream stats off of wt.getStats() and we're discussing per-stream-level stats off of readable.getStats() and writable.getStats() that will mostly contain byte progress counters in #372.

Neither of those approaches should be difficult to traverse, nor should stats disappear (one caveat: the per-stream stats are meant for long-lived streams, for short-lived ones we have aggregate stats at the connection level).

We have 5 other issues on stats so I think we can close this one.

from webtransport.