Re: [httpwg/http-extensions] HTTP/2 PUSH cache mechanism? (#174)
HTTP issue updates <http-issues@ietf.org> Thu, 21 April 2016 14:17 UTC
Delivered-To: http-issues@ietfa.amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.928
X-Spam-Level:
X-Spam-Status: No, score=-5.928 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_16=1.092, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Date: Thu, 21 Apr 2016 07:17:03 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1461248223; bh=qulgt/mpFu8fv0enchZYf6+tt3aOIRJ+WxblnLxJ9g8=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Vt0N26zYP3GaqKIP1R/uYdNIPoc8oZO1Hi5lxCuXMzqrd1Y/RIlCGJ5HmOSjcDvGq cgnV24Luoojhed1XGRQGEKjjCExmYX+zqoo5VxxVLjStHiGQWKWkhELnrFGyLld3IB ZDNuIk+ebQhubdML0GEzr3b4SfOVwWSXDgi//3EI=
To: httpwg/http-extensions <http-extensions@noreply.github.com>
In-Reply-To: <httpwg/http-extensions/issues/174@github.com>
References: <httpwg/http-extensions/issues/174@github.com>
Subject: Re: [httpwg/http-extensions] HTTP/2 PUSH cache mechanism? (#174)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5718e0df896ca_42553f9a065b72c03641b7"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <http://mailarchive.ietf.org/arch/msg/http-issues/BE7LZWvvdUBHUxB9PbUvnDrdR0Y>
Message-ID: <mailman.1718.1461248226.4402.http-issues@ietf.org>
From: HTTP issue updates <http-issues@ietf.org>
X-BeenThere: http-issues@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: http-issues@ietf.org
List-Id: HTTP issue updates <http-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/http-issues>, <mailto:http-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/http-issues/>
List-Post: <mailto:http-issues@ietf.org>
List-Help: <mailto:http-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/http-issues>, <mailto:http-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Apr 2016 14:17:06 -0000
Ok, just saw your response; you are focusing on the http layer cache. yes, it's part of several discussions I would say. This was presented at Buenos Aires https://datatracker.ietf.org/doc/draft-kazuho-h2-cache-digest/. The use of Link header to inform a client about such stufff as an ODG has been mentioned. Expect it to be a piece of the puzzle here. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/issues/174#issuecomment-212938504
- [httpwg/http-extensions] HTTP/2 PUSH cache mechan… HTTP issue updates
- Re: [httpwg/http-extensions] HTTP/2 PUSH cache me… HTTP issue updates
- Re: [httpwg/http-extensions] HTTP/2 PUSH cache me… HTTP issue updates
- Re: [httpwg/http-extensions] HTTP/2 PUSH cache me… HTTP issue updates