IETF Logo Mail Archive

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 09:19 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 AF48D120110 for <quic-issues@ietfa.amsl.com>; Wed, 22 May 2019 02:19:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.392
X-Spam-Level:
X-Spam-Status: No, score=-6.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_HI=-5, 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 flWhLstB5M3P for <quic-issues@ietfa.amsl.com>; Wed, 22 May 2019 02:19:29 -0700 (PDT)
Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38656120105 for <quic-issues@ietf.org>; Wed, 22 May 2019 02:19:29 -0700 (PDT)
Date: Wed, 22 May 2019 02:19:28 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1558516768; bh=VJZySPC6Nu7CSL4HjP+HwJfmOzWEHrOQ5B21jjXydqA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=0XNzHDra234vjj6DMP637EFfmEF7RQ51CGWIiw824InOfzKoDcd1Snk1hzp78+9yO qc0lZAN1YThroWn5H4uapgB6PogTjSIA2MqIy+SjYZFVtM8EmSqe0yXlaaKBrVQYEd y/HBKJL42F0X8R34ra99C8pprgBaF+PLA0UWVvcM=
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK5EEQC7ZWRUIS7TT5526JDKBEVBNHHBVIUZ3Y@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/494723596@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_5ce514201d8a3_3c373fd9ff4cd95c16066f5"; 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/rlJQzs48YvFQQ7i4qYUvyV4b0uI>
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 09:19:31 -0000

I agree with the points Ian has captured in the issue.

@mikkelfj I don't really understand your question. To use a simple case, are you asking about the difference between the browser's resource loading strategies for HTML vs Fetch/XHR? 


-- 
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-494723596

v2.15.0 | Report a Bug | By Email