Subject: [quicwg/base-drafts] Multiple server pushes (#702)

From: Martin Thomson <[email-masked]>
Date: Thu, 27 Jul 2017 06:29:10 +0000 (UTC)

@kazuho pointed out that because there is no ordering between streams, you can have the need to trigger a server push on multiple streams.  If two concurrent requests identify the same subresource, then you end up having to push that subresource twice.  That's inefficient.

This is less of a problem in h2 where the server could push for the first response and avoid pushing on the second.  Strict ordering means that it knows that the client has at least seen the PUSH_PROMISE for the first response.  Of course, it's not a perfect design: routing of the responses at the client might mean that the they might be consumed by different entities, leading to the possibility that the second doesn't get a chance to see the push.

-- 
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/issues/702