Re: [quicwg/base-drafts] Why are there two ways of associating push with requests? (#3275)

Lucas Pardue <> Wed, 27 November 2019 13:09 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 217BB120872 for <>; Wed, 27 Nov 2019 05:09:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Status: No, score=-6.454 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id xgpKyMD6RfAl for <>; Wed, 27 Nov 2019 05:09:55 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 498DB12083F for <>; Wed, 27 Nov 2019 05:09:55 -0800 (PST)
Date: Wed, 27 Nov 2019 05:09:54 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1574860194; bh=V0rFU52ur5rPvcOQwra82Y4XMevARMf1c2NdChEdqds=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=McSL9sATL27VC1RVxMPos4sgfWMHYgTgESFWeSMnCY9bBnGIbiwcr4IwRKXZxTIbR 2kC7vt7n6W0TuioPVaqgssug4ScU/NOiWjX/s03I1Ir/fpq1Tjbyi/Zs1g2JAREQNe M2oREI8ikuHAfpDYNATvtJ/0OtLqyVjM/M3BjKU4=
From: Lucas Pardue <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3275/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Why are there two ways of associating push with requests? (#3275)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dde75a26783c_7b853fb93bacd968181978"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: LPardue
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 27 Nov 2019 13:09:57 -0000

Since you mention priority, the other question I have is at what priority is the pushed response delivered at? For example, with the proposal, the server gets request A (low precedence) and B (high precedence) it responds with unified PUSH_PROMISE on both A and B, which priority does the client believe the server is delivering the push stream with?

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: