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

Lucas Pardue <> Wed, 27 November 2019 11:56 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 346AB120893 for <>; Wed, 27 Nov 2019 03:56:02 -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 ixx06mqiK7aa for <>; Wed, 27 Nov 2019 03:56:00 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id AC8E412088D for <>; Wed, 27 Nov 2019 03:56:00 -0800 (PST)
Date: Wed, 27 Nov 2019 03:55:59 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1574855759; bh=TAixpjAs5PA6rq8IgodLt6AIxAKd8bWPKmedtKef8zc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=VgTAnKj4/WqAbx4kV63Wkx8WaDE0tjfvr1iQbrxZx+eBLRV+RgyOPk5BQ//KNALf3 0MWXdjLI3bt60OzixVdkZMOWy2kvQ5wrkBPQ2VYW47UdQqM3EWi4CvmOxTIPC+kgYW XIlKtfvWaX+v6gpd0DBKhThTIaheLmFIyEDeJAzo=
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_5dde644fc0b0a_77523fe0620cd960106359"; 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 11:56:02 -0000

> Send the request of a push on the "push stream," instead of sending it using PUSH_PROMISE.

How would you do this? With a HEADERS frame, or some new frame type? The reason I ask is because it would seem to change the message ordering that we have defined today (HEADERS, DATA, HEADERS)

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