Re: Concepts to improve Http2.0
Dennis Olvany <dennisolvany@gmail.com> Wed, 27 July 2016 13:08 UTC
Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F72A12D1A4 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 27 Jul 2016 06:08:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.307
X-Spam-Level:
X-Spam-Status: No, score=-8.307 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 YH96kMMYMOlo for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 27 Jul 2016 06:08:16 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F74412B00D for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 27 Jul 2016 06:08:16 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1bSOV3-0008DN-MV for ietf-http-wg-dist@listhub.w3.org; Wed, 27 Jul 2016 13:03:49 +0000
Resent-Date: Wed, 27 Jul 2016 13:03:49 +0000
Resent-Message-Id: <E1bSOV3-0008DN-MV@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <dennisolvany@gmail.com>) id 1bSOUx-0008Cg-C4 for ietf-http-wg@listhub.w3.org; Wed, 27 Jul 2016 13:03:43 +0000
Received: from mail-it0-f41.google.com ([209.85.214.41]) by lisa.w3.org with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <dennisolvany@gmail.com>) id 1bSOUo-0006xK-7i for ietf-http-wg@w3.org; Wed, 27 Jul 2016 13:03:42 +0000
Received: by mail-it0-f41.google.com with SMTP id f6so22684948ith.0 for <ietf-http-wg@w3.org>; Wed, 27 Jul 2016 06:03:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=Br2SPRJZgZxhSpPQ5KGehl9Nw5aRLpA+xHuiEMehHO4=; b=kIDumtPFzqABeXUJjA6yT+kyuDArRx2ATiykPvlkZ13Agc83cRLaPwi/TUWCdCqg/Q 0kmubcWa4m7UvpoqeHRp9b8EoRDasCEqRO7Ufilf5GMDtVx94Mxog8ZiKhxUXl3d9O5u D4L3xJJTunEwuIe43j1fCrnscjHGc7XLUXnQQHM1POSabSZMCTbnTPRqTtccw4RTHWbz deHtY6F3t734dvMiERXLzAn+IZhdMP1Enbxk7OGZ4PwEVOdYpz7iJH2Jbt0vNQGNTlxo 1R77UTJnV4si5NOMowQdYIIQwtKbe1ChRAd9z5cCLK9eFTHFhkt9IbhfcAE+vlfHs+8f rugQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=Br2SPRJZgZxhSpPQ5KGehl9Nw5aRLpA+xHuiEMehHO4=; b=BIK1T+X8U3u+H2yI8IfayKtGquluam4Cgf8qXKQdqpXleYygdC3q5ANtVj9/h9/0F4 42M7RDW8Z3LTHIGcko8ULQciF5gP5zkL4lew7Qh6oFrCpDRv4WBNFAWdQMBOfrLMR2CF b+2fLoctrszhao5uFQfsuiMyE8iJqS3BkLCmdDXMIt2lu9FU6UDViVyGQNptyo7bixJX vrh6KjhOwRLD91mkbNznTwTHx9UaQGA1zUKAeBug1weiem5slQEq7BNDiXJ1xZ4SbYCR QXj/5mD6eGH+re4RualgE8Dz+NZz3x6DQ5d5oZ3j8mHZxRg9yOP1Wm74fUDzw2ug1Q6z LVtg==
X-Gm-Message-State: ALyK8tJXahT9lpQFqNUq96PNZB/5qWiWBo9X9jPWZIRtE+b3X7xL+vHBmJ1pOEz4sZIcnyjHKpSRm2c2LS0wtw==
X-Received: by 10.36.120.199 with SMTP id p190mr75571673itc.7.1469624587809; Wed, 27 Jul 2016 06:03:07 -0700 (PDT)
MIME-Version: 1.0
References: <CACvHZ2bkgJcySp7gBVNZ10hbUmKyu0ZQiT_UunXB0yMYre795Q@mail.gmail.com> <7CF7F94CB496BF4FAB1676F375F9666A2A838589@bgb01xud1012>
In-Reply-To: <7CF7F94CB496BF4FAB1676F375F9666A2A838589@bgb01xud1012>
From: Dennis Olvany <dennisolvany@gmail.com>
Date: Wed, 27 Jul 2016 13:02:58 +0000
Message-ID: <CAATNdDyKzoAtHCORdnmx2zCJpqiT7XvN7OxJ1N8XP14ykYyzpw@mail.gmail.com>
To: Lucas Pardue <Lucas.Pardue@bbc.co.uk>, Wesley Oliver <wesley.olis@gmail.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="001a114a920882a77d05389da39a"
Received-SPF: pass client-ip=209.85.214.41; envelope-from=dennisolvany@gmail.com; helo=mail-it0-f41.google.com
X-W3C-Hub-Spam-Status: No, score=-5.0
X-W3C-Hub-Spam-Report: AWL=-1.315, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: lisa.w3.org 1bSOUo-0006xK-7i 8cc2e61d02e9777f5697f9c942d10fb3
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Concepts to improve Http2.0
Archived-At: <http://www.w3.org/mid/CAATNdDyKzoAtHCORdnmx2zCJpqiT7XvN7OxJ1N8XP14ykYyzpw@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/32050
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
Wesley, You may be interested in the following document. https://tools.ietf.org/html/draft-kazuho-h2-cache-digest-01 On Wed, Jul 27, 2016 at 6:27 AM Lucas Pardue <Lucas.Pardue@bbc.co.uk> wrote: > Hi Wesley, > > > > I had a look over your document. > > > > Is the crux of your problem statement that you want to send out > dynamically generated content as early as possible? Could your problem be > solved by the use of chunked transfer encoding and Trailers [1]? In HTTP/2 > frame format, the simplest response would be a series of frames such as > HEADERS, DATA, HEADERS (Trailers with END_STREAM flag). This is explained > in more detail in RFC 7540 section 8.1 [2]. > > > > In the examples included in your document there are multiple “Dependent > Resources” that get pushed. Are these independent static resources that the > dynamic generated content refers to? > > > > As far as my understanding goes the current protocol mechanisms should > permit chunked transfer and push promises without needing to modify the > stream life cycle. Pushed resources would sit in the client cache ready to > be used by the dynamically generated content when it is received and > parsed. In other words, you could achieve your proposed improvemed timing > diagram with current mechanisms. > > > > Regards > > Lucas > > > > [1] https://tools.ietf.org/html/rfc7230#section-4.1.2 > > [2] https://tools.ietf.org/html/rfc7540#section-8.1 > > > > > > *From:* Wesley Oliver [mailto:wesley.olis@gmail.com] > *Sent:* 27 July 2016 07:20 > *To:* ietf-http-wg@w3.org > *Subject:* Concepts to improve Http2.0 > > > > Hi, > > > > I am not new to the concept of the IETF, however, I have yet to make an > offical submission. > > > > I would like to put forth a concept that can further improve the > performance of http 2.0. > > I have a couple of other concepts as well regarding content expiry headers > which would affect http 1.1. > > Additionally I would also like to look into concepts to prevent > unnecessary push requests for content that is already cached by the > browser. Since mobile bandwidth constraints, would be obviously benefit > from not push content that is already cached. > > > > Full document on the concept can be found at the link below and first > abstract can be found to follow this email. > > > > > https://docs.google.com/document/d/1xGY4GycBMt4zyCoJpzoIZrlLOs1bwaRVBfPE9aXdbyE/edit?usp=sharing > > > > If you could please advise as to the path to follow. > > > > > > Kind Regards, > > > > Wesley Oliver > Http Response Stream - Optimistic approach for performance improvement and > Snowball effect of Response Body Programming paradigm shift of benefits > > *Abstract* > > > > Traditionally in http 1.1 one is required to buffer an http response on > the server side. If a change to the headers was to be made during the > response somewhere during the page generation code, because headers are not > allowed to be changed after the message-body has been transmitted. Changing > these semantics by removing this constraint in http 2.0 will open the door > to an http response programming paradigm shift in possibilities. Benefits, > improved and optimal bandwidth utilization, reduce overall page render > resource latency and potentially an increase in server page requests that > can be processed. > Concept: > > Allow multiple response to be sent over the wire for the same request, > whereby the last response that has been transmitted over the wire, will > form the official response that will be permanently rendered in the client > browser. > > > > This is an optimistic approach, when the response will not change, > therefore eliminating the need to buffer the response. As soon as network > buffer has a full packet or has been forced flushed it can be transmitted > over the wire, reducing the latency of the response experience by the > client. Additionally it also allows for improved bandwidth utilization > after the server has received the request, as it can immediately start > sending response packets, reducing potentially wasted bandwidth during the > time in which the response is being generated and then buffered before > transmission. > > > > > > > > > > -- > > -- > Web Site that I have developed: > http://www.swimdynamics.co.za > > > Skype: wezley_oliver > MSN messenger: wesley.olis@gmail.com > > > > ---------------------------- > > http://www.bbc.co.uk > This e-mail (and any attachments) is confidential and may contain personal > views which are not the views of the BBC unless specifically stated. > If you have received it in error, please delete it from your system. > Do not use, copy or disclose the information in any way nor act in > reliance on it and notify the sender immediately. > Please note that the BBC monitors e-mails sent or received. > Further communication will signify your consent to this. > > --------------------- >
- Re: Concepts to improve Http2.0 Matthew Kerwin
- Re: Concepts to improve Http2.0 Wesley Oliver
- Re: Concepts to improve Http2.0 Martin J. Dürst
- Re: Concepts to improve Http2.0 Patrick McManus
- Re: Concepts to improve Http2.0 Patrick McManus
- Re: Concepts to improve Http2.0 Wesley Oliver
- Re: Concepts to improve Http2.0 Wesley Oliver
- Re: Concepts to improve Http2.0 Amos Jeffries
- Re: Concepts to improve Http2.0 Amos Jeffries
- Re: Concepts to improve Http2.0 Mark Nottingham
- Re: Concepts to improve Http2.0 Wesley Oliver
- Re: Concepts to improve Http2.0 Cory Benfield
- Re: Concepts to improve Http2.0 Wesley Oliver
- Re: Concepts to improve Http2.0 Amos Jeffries
- Re: Concepts to improve Http2.0 Cory Benfield
- Re: Concepts to improve Http2.0 Wesley Oliver
- Re: Concepts to improve Http2.0 Poul-Henning Kamp
- Re: Concepts to improve Http2.0 Adrien de Croy
- Re: Concepts to improve Http2.0 Dennis Olvany
- RE: Concepts to improve Http2.0 Lucas Pardue
- Concepts to improve Http2.0 Wesley Oliver