Date: Wed, 27 Nov 2019 12:34:13 -0800
From: Ryan Hamilton <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+AFTOJK3Y4DTPQSHKGY2FJOF35QIELEVBNHHB7DC6LI@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3275/559242203@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3275@github.com>
References: <quicwg/base-drafts/issues/3275@github.com>
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_5ddeddc569f10_277e3fcc740cd96c25441f";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/QQeuegl6vy-1uU16xt0dlkeI9Qk>


----==_mimepart_5ddeddc569f10_277e3fcc740cd96c25441f
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

That seems like a show-stopper to me. Push is full of sharp edges already and this would add another one. I think we need a guarantee that if the server is pushing a URL, the client knows about it before it makes a request for that resource.

-- 
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/3275#issuecomment-559242203
----==_mimepart_5ddeddc569f10_277e3fcc740cd96c25441f
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p>That seems like a show-stopper to me. Push is full of sharp edges already and this would add another one. I think we need a guarantee that if the server is pushing a URL, the client knows about it before it makes a request for that resource.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/quicwg/base-drafts/issues/3275?email_source=notifications&amp;email_token=AFTOJKZLAWYDUSMDSWKYLILQV3KULA5CNFSM4JSFRKX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFKVXWY#issuecomment-559242203">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AFTOJK5RMOBLHY7VXADQPW3QV3KULANCNFSM4JSFRKXQ">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AFTOJK57JXS6ND6K4M2AU7LQV3KULA5CNFSM4JSFRKX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFKVXWY.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/issues/3275?email_source=notifications\u0026email_token=AFTOJKZLAWYDUSMDSWKYLILQV3KULA5CNFSM4JSFRKX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFKVXWY#issuecomment-559242203",
"url": "https://github.com/quicwg/base-drafts/issues/3275?email_source=notifications\u0026email_token=AFTOJKZLAWYDUSMDSWKYLILQV3KULA5CNFSM4JSFRKX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFKVXWY#issuecomment-559242203",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5ddeddc569f10_277e3fcc740cd96c25441f--