Re: [quicwg/base-drafts] Deadlocks, and how to avoid them (#3458)

ianswett <notifications@github.com> Fri, 14 February 2020 17:49 UTC

Date: Fri, 14 Feb 2020 09:49:28 -0800
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK22AVQWXUKZ3FD6OVV4KQICREVBNHHCDLNOLI@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3458/review/359109199@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3458@github.com>
References: <quicwg/base-drafts/pull/3458@github.com>
Subject: Re: [quicwg/base-drafts] Deadlocks, and how to avoid them (#3458)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e46dda816330_10473fdbb62cd964698e2"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/oGdYAaGQaZ3qfrEIKshanALBBS8>

ianswett commented on this pull request.

Thanks for adding this!

> @@ -281,6 +281,26 @@ table entries which have been acknowledged, but this could mean using
 literals. Since literals make the header block larger, this can result in the
 encoder becoming blocked on congestion or flow control limits.
 
+### Avoiding Flow Control Deadlocks
+
+Encoding using blocked streams can interact with flow control to produce

```suggestion
Writing instructions on blocked or soon to be blocked streams can interact with flow control to produce
```

-- 
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/3458#pullrequestreview-359109199

[quicwg/base-drafts] Deadlocks, and how to avoid … Martin Thomson
Re: [quicwg/base-drafts] Deadlocks, and how to av… Martin Thomson
Re: [quicwg/base-drafts] Deadlocks, and how to av… ianswett
Re: [quicwg/base-drafts] Deadlocks, and how to av… Martin Thomson
Re: [quicwg/base-drafts] Deadlocks, and how to av… afrind