mirror of
https://github.com/golang/net.git
synced 2026-03-31 10:27:08 +09:00
8a4d9c198f
In RFC 9218, streams are non-incremental by default, meaning that they are processed one-by-one to completion. This behavior is the opposite of our current default of handling streams in a round-robin manner. This might cause a surprising behavior change once we make the RFC 9218 priority scheduler the default write scheduler for most users (we assume that most users will not be sending RFC 9218 priority signals, at least initially). To avoid surprising users with such a behavior change, this CL makes it so that the streams are only made non-incremental once there has been a clear signal that the end-user is aware of RFC 9218. For golang/go#75500 Change-Id: Ibd22cb279c43de0190962904c3809007447a5fe3 Reviewed-on: https://go-review.googlesource.com/c/net/+/729140 Reviewed-by: Michael Knyszek <mknyszek@google.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Damien Neil <dneil@google.com> Reviewed-by: Nicholas Husin <husin@google.com>