Re: [quicwg/base-drafts] Application can reset stream or close connection even if no error occurs. (#3953)

[Bence Béky <[e-mail]>]

@bencebeky commented on this pull request.



> +Section 11 of {{QUIC-TRANSPORT}}) and has an associated error code, but does not
+necessarily have to be an error.  For example, a stream can be reset if the

I agree with you.  My interpretation is that the source of strangeness is calling these stream errors and connection errors in the first place, and calling their reason codes error codes.  This way "error" becomes a technical term defined in this document, which does not align with my mental model of what an error is: entry found is cache or user closing a tab or navigating away is clearly not an error, but the specs treat it is a stream error and assign an error code to it.

Unfortunately I cannot think of a less weird way of phrasing it.  "Do not necessarily have to be abnormal events or protocol violations."?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/3953#discussion_r460003741