Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
 by ietfa.amsl.com (Postfix) with ESMTP id 5EE16120074
 for <quic-issues@ietfa.amsl.com>; Tue, 21 May 2019 23:16:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.464
X-Spam-Level: 
X-Spam-Status: No, score=-1.464 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, 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, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01]
 autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key)
 header.d=github.com
Received: from mail.ietf.org ([4.31.198.44])
 by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id zF5HFiN4_Oi9 for <quic-issues@ietfa.amsl.com>;
 Tue, 21 May 2019 23:16:05 -0700 (PDT)
Received: from out-20.smtp.github.com (out-20.smtp.github.com [192.30.252.203])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id C13BE1200E6
 for <quic-issues@ietf.org>; Tue, 21 May 2019 23:16:04 -0700 (PDT)
Date: Tue, 21 May 2019 23:16:03 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
 s=pf2014; t=1558505763;
 bh=qig6OyGpNqrcnjGIJTtPU0CjpRId4cnr0pAqk3oVczM=;
 h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID:
 List-Archive:List-Post:List-Unsubscribe:From;
 b=L5BzyPtc5Gglmy2K130hsKyUaOPK5Q2Czu97eGd9yJvX8l5pcjPMhOAYkZkd3n31d
 /zb61KC3Kf6Kg+Mq6qvCxM5q1sT3o68w/53TzEKqsZlXSvdV47urN5lG0d4NUD2/Fa
 2TOo9ZQuV2AAWNlBe1KG8ZQkUEyExC3j9IgiWb2k=
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+AFTOJKZKAJQMIJYYPGJG2PN26IN2HEVBNHHBVIUZ3Y@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2739/494667204@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2739@github.com>
References: <quicwg/base-drafts/issues/2739@github.com>
Subject: Re: [quicwg/base-drafts] HTTP/3 priorities are too complex for a
 majority of implementations (#2739)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5ce4e923570f9_6d133fb1812cd9641001038";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/hjZwHHhJjAmdhvN_YEvepwl-6y4>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG
 <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>,
 <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>,
 <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 May 2019 06:16:08 -0000


----==_mimepart_5ce4e923570f9_6d133fb1812cd9641001038
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

How much is there to gain by complex priorities where the browser has to guess vs javascript controlled lazy loaders that now the sites requirements exactly?

-- 
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/2739#issuecomment-494667204
----==_mimepart_5ce4e923570f9_6d133fb1812cd9641001038
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p>How much is there to gain by complex priorities where the browser has to guess vs javascript controlled lazy loaders that now the sites requirements exactly?</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/2739?email_source=notifications&amp;email_token=AFTOJK5SZ35Y3D4GN67HEV3PWTQKHA5CNFSM4HOPM3R2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV6ALRA#issuecomment-494667204">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AFTOJKZHYTWSJZWDNYJ7TVLPWTQKHANCNFSM4HOPM3RQ">mute the thread</a>.<img src="https://github.com/notifications/beacon/AFTOJK6C4T5E4PVIIRQ74A3PWTQKHA5CNFSM4HOPM3R2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV6ALRA.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/2739?email_source=notifications\u0026email_token=AFTOJK5SZ35Y3D4GN67HEV3PWTQKHA5CNFSM4HOPM3R2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV6ALRA#issuecomment-494667204",
"url": "https://github.com/quicwg/base-drafts/issues/2739?email_source=notifications\u0026email_token=AFTOJK5SZ35Y3D4GN67HEV3PWTQKHA5CNFSM4HOPM3R2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV6ALRA#issuecomment-494667204",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5ce4e923570f9_6d133fb1812cd9641001038--

