Re: [quicwg/base-drafts] HTTP/3 priorities are too complex for a majority of implementations (#2739)
Lucas Pardue <notifications@github.com> Wed, 22 May 2019 11:33 UTC
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 DB68F12011C for <quic-issues@ietfa.amsl.com>; Wed, 22 May 2019 04:33:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.392
X-Spam-Level:
X-Spam-Status: No, score=-1.392 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_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 Djgdct0r-Ro5 for <quic-issues@ietfa.amsl.com>; Wed, 22 May 2019 04:33:11 -0700 (PDT)
Received: from out-23.smtp.github.com (out-23.smtp.github.com [192.30.252.206]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB5E512004D for <quic-issues@ietf.org>; Wed, 22 May 2019 04:33:10 -0700 (PDT)
Date: Wed, 22 May 2019 04:33:09 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1558524790; bh=Cb+fai5xSCHl8vwJyLeOBjJveaDkU9s4Ji9L9rQ9984=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=VdzCCZtHDsTYdP8Avp+mb+n7zigj8m2TZzknzHcqzzgP0jd6jLcQC2TBR5XMZDhvv nnTNRxcWOmbyFGk4wl2rvJloJOYPlIyFMdOhuCViDBZ9Ks663hTSA/jKVSVsX5LJuL qIlQU49iQhh5rqsu1Bursq5jkobVvFwq7SBQNrMc=
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKY2IBY6A23OZNRXOA526JS7LEVBNHHBVIUZ3Y@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/494764518@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_5ce53375eb696_119c3fb1812cd96480921c"; 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
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/zz7UbhNSToI9EOG8iHwlkmYKtz8>
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 11:33:12 -0000
It's good that there are ways to improve performance in such ways. However, I think that the HTTP/3 layer should allow prioritisation of resource loading. That way it applies to all user agents, not just those that have a DOM and or JavaScript engine. > Also, I feel this is a separate topic that might require a different issue to not take away from the core issue being discussed here. Agreed. -- 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-494764518
- [quicwg/base-drafts] HTTP/3 priorities are too co… ianswett
- Re: [quicwg/base-drafts] HTTP/3 priorities are to… MikkelFJ
- Re: [quicwg/base-drafts] HTTP/3 priorities are to… Lucas Pardue
- Re: [quicwg/base-drafts] HTTP/3 priorities are to… MikkelFJ
- Re: [quicwg/base-drafts] HTTP/3 priorities are to… Lucas Pardue
- Re: [quicwg/base-drafts] HTTP/3 priorities are to… MikkelFJ
- Re: [quicwg/base-drafts] HTTP/3 priorities are to… Robin Marx
- Re: [quicwg/base-drafts] HTTP/3 priorities are to… Lucas Pardue
- Re: [quicwg/base-drafts] HTTP/3 priorities are to… Patrick Meenan
- Re: [quicwg/base-drafts] HTTP/3 priorities are to… Mike Bishop