Re: Server push limited to cache priming?

• From: Martin J. Dürst <duerst@it.aoyama.ac.jp>
• Date: Mon, 24 Mar 2014 18:38:17 +0900
• To: Roberto Peon <grmocg@gmail.com>
• CC: Daniel Sommermann <dcsommer@fb.com>, HTTP Working Group <ietf-http-wg@w3.org>
• Message-ID: <532FFD09.7060603@it.aoyama.ac.jp>

On 2014/03/20 10:10, Roberto Peon wrote:
> I'm not too worried about this.
> The types of things that would really use server-initiated streams but not
> push something into a cache are the kinds of things best served with the
> WebSocket API or something similar.

Hello Roberto,

I agree that currently, these kinds of things are best served with the 
WebSocket API. But using the WebSocket API means throwing away 
addressability (linking, bookmarking, searchability,...) and caching.

There are applications that can benefit both from a true push channel 
(e.g. the WebSocket server->client direction or HTTP2 PUSH) and from 
addressability and caching.

And combining these may have other benefits, such as greater ease of 
reconnecting after the connection is broken. WebSocket currently leaves 
this completely up to the application.

Regards,   Martin.

Received on Monday, 24 March 2014 09:38:52 UTC