Re: [quicwg/base-drafts] Allow the Transport to Stop/Reset a Stream? (#3291)

[Nick Banks <[e-mail]>]

Imagine a C++/C# Stream class/object in an intermediate library between the app and the native C transport library. The transport indicates a C object to the intermediate library, then the intermediate library creates it's own object/wrapper, but something fails along the way that's not fatal to the entire connection. The app layer is not yet in the picture, but the intermediate library cannot continue with the stream. I see these possible options:

1. Upcall to the app (or allow the app to pre-configure) to get an appropriate error code to terminate the stream with.
2. Terminate the entire connection even though it's a stream specific problem (but this has the same problem, because the error code would have to be app specific, so we'd have to expose an API to allow the intermediate layer to issue a transport connection close).
3. Change the protocol to allow a non-app specific error code to be used to terminate the stream.

-- 
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/issues/3291#issuecomment-562877033