Closed GrumpyOldTroll closed 2 years ago
I think this issue is mostly(?) addressed by removing the STREAM_BOUNDARY (https://github.com/GrumpyOldTroll/draft-jholland-quic-multicast/issues/28), and now server is required to buffer data that still needs to be sent to clients, but we do not operationally expect this data to accumulate in channels since the streams in channels will be reset when no longer needed.
We might need to make a comment in the operational considerations section saying that the server shouldn't do things that require infinite buffering, but I'll make a separate issue from there.
Session data needs reliability on streams, but also servers need to not be required to buffer unbounded amounts of data. Define what the failure modes look like.