W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2018

Push Use Cases

From: Mike Bishop <mbishop@evequefou.be>
Date: Fri, 29 Jun 2018 23:06:37 +0000
To: HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <BYAPR08MB39441F4BDBD20DA5D7572936DA4E0@BYAPR08MB3944.namprd08.prod.outlook.com>
This draft isn't targeted for a protocol standard so much as enumerating different ways to use push.  HTTP/2 provides the mechanics of pushing a request/response pair that the client hasn't asked for yet, but... what exactly does that request look like, and what does a client actually *do* with it?

Pretty much the only thing that has coalesced is dependent resources on the same page.  Pushing responses to XHR queries, pushing cache validation updates or invalidations, etc. are things that we've handwaved about and never really defined.

This draft is an effort to enumerate the different ways that push *could* be used, in hopes that it can develop into a common reference to describe what each client supports or doesn't.

-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Friday, June 29, 2018 3:54 PM
To: Mike Bishop <mbishop@evequefou.be>
Subject: New Version Notification for draft-bishop-httpbis-push-cases-00.txt


A new version of I-D, draft-bishop-httpbis-push-cases-00.txt
has been successfully submitted by Mike Bishop and posted to the IETF repository.

Name:		draft-bishop-httpbis-push-cases
Revision:	00
Title:		HTTP/2 Server Push Use Cases
Document date:	2018-06-28
Group:		Individual Submission
Pages:		6
URL:            https://www.ietf.org/internet-drafts/draft-bishop-httpbis-push-cases-00.txt
Status:         https://datatracker.ietf.org/doc/draft-bishop-httpbis-push-cases/
Htmlized:       https://tools.ietf.org/html/draft-bishop-httpbis-push-cases-00
Htmlized:       https://datatracker.ietf.org/doc/html/draft-bishop-httpbis-push-cases


Abstract:
   HTTP/2 defines the wire mechanics of Server Push.  Though the
   mechanics of how a pushed resource is delivered are well-specified,
   the use cases that describe which resources can be pushed, in what
   states, and for what purpose are not described in HTTP/2.  As a
   result, support between implementations varies widely.

   This document attempts to enumerate interesting scenarios, in hopes
   that a more concrete taxonomy can assist the community in arriving at
   a standard set of supported scenarios.

                                                                                  


Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

Received on Friday, 29 June 2018 23:07:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:15:21 UTC