On Sat, Jun 7, 2025, at 14:52, Marten Richter wrote: > Am 07.06.2025 um 04:50 schrieb Kazuho Oku: >> >> The practical disadvantage of WT/H1 is that it incurs one additional >> RT for setup. This is because the server can send the initial flow >> control credits only after receiving the HTTP request. WT/H2 avoids >> this problem by allowing servers to send their credits using H2 >> SETTINGS, but there is nothing that we can use on H1. >> ----------- > You can send immediately capsules with the corresponding settings, that > is how I emulate it with websockets.
That is inadvisable for the reasons described in https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-optimistic-upgrade-03. That is, a server can send its capsules as soon as it accepts the request, but the client cannot do the same thing.
