Re: [quicwg/base-drafts] HTTP/3 priorities are too complex for a majority of implementations (#2739)

MikkelFJ <> Wed, 22 May 2019 11:22 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0099B120131 for <>; Wed, 22 May 2019 04:22:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.392
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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Jg7pGDgKwSkk for <>; Wed, 22 May 2019 04:22:01 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 7142A12004D for <>; Wed, 22 May 2019 04:22:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed;; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=jqbM1Nw1S86q05K5kFvWgVPH5uk=; b=I+2f7ckZ7+aYo5WH kXosbBrvANKugltqJQ4B/GgetuvY6/RvM22/k76kFwH6XdtGQqKlBv4K2PVjmWpv eBABtP1SdE4pWW+qVXErWJH8Dyn9dNO6ge3lmsHdHBjJMdZ7wchIX6it9ibcHQ+K Y3GNKMMoG4EfLQOkjbTCjx1St9c=
Received: by with SMTP id filter1745p1mdw1-5464-5CE530D6-2D 2019-05-22 11:21:58.467951015 +0000 UTC m=+128145.206740839
Received: from (unknown []) by (SG) with ESMTP id iIY5q2TVSBaUNW35jy5Y5g for <>; Wed, 22 May 2019 11:21:58.365 +0000 (UTC)
Received: from (localhost []) by (Postfix) with ESMTP id 69CB03400FD for <>; Wed, 22 May 2019 04:21:58 -0700 (PDT)
Date: Wed, 22 May 2019 11:21:58 +0000
From: MikkelFJ <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2739/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
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_5ce530d667e9f_2c73fd090acd9601258723"; 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-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0SrbALakcdjuwa6szdhtEWIsQ08jVd1gLFE9 ZPr/wGT0WGsJk0vJ67HCxakPKMPxstB7Su3okBk3xjEEzhKrPoES4uOM6dpd6DCyBm4GxvDml8yd3R dbMqwcn3RTtq2c13625XECqTADFIYVWI4GOAA7XPM9mShuwkI18DL+LmdQ==
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, 22 May 2019 11:22:03 -0000

I have practical experience with this. I was working on a startup where page load times consistently ranked very high using this approach. It was combined with redirecting resources to a CDN network off the main server and using image scaling to match the target device.

The downside is that it does require javascript and modifications to web content. In this case it was limitd to a single config object, a very small javascript loader, and tag prefixing like <cdn:img ...> instead of <img >.

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