- From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
- Date: Tue, 29 Jan 2019 16:13:46 -0500
- To: Patrick Meenan <patmeenan@gmail.com>
- Cc: Lucas Pardue <lucaspardue.24.7@gmail.com>, Amos Jeffries <squid3@treenet.co.nz>, HTTP Working Group <ietf-http-wg@w3.org>
On Tue, Jan 29, 2019 at 02:53:55PM -0500, Patrick Meenan wrote:
> As far as I can tell, the placeholder streams serve to handle the Firefox
> use case of using idle streams for groupings, not to eliminate the need to
> synchronize tree states. When you chain streams after each other (the
> Chrome case) you need to make sure the stream you are attaching to is still
> known by the server.
The solution is to use placeholders: do not make one stream depend
on another, but put a placeholder in between.
Some Node -> Stream A -> Placeholder X -> Stream B
If Stream A goes away, Stream B is not moved:
Some Node -> Placeholder X -> Stream B
- Dmitri.
Received on Tuesday, 29 January 2019 21:14:10 UTC