Hi, Roland and Richard: how the following two documents are related to each other? draft-schott-alto-new-transport-push-00 => ALTO New Transport: Server Push using PUSH_PROMISE of HTTP/2 RFC8895 => ALTO Incremental Updates Using Server-Sent Events (SSE) My impression is RFC8895 only use multiplexing feature in HTTP /2 and SSE defined in W3C as the basic server-push design, Server PUSH feature in HTTP/2 is not used, while draft-schott focus on PUSH promise feature in HTTP/2
RFC8895 said: " An HTTP/2 client library may not necessarily inform a client application when the server pushes a resource. Instead, the library might cache the pushed resource and only deliver it to the client when the client explicitly requests that URI. Further, it is more likely that a design based on HTTP/2 may encounter issues with a proxy between the client and the server, in that server push is optional and can be disabled by any proxy between the client and the server. This is not a problem for the intended use of server push; eventually, the client will request those resources, so disabling server push just adds a delay. But this means that Server Push is not suitable for resources that the client does not know to request. Thus, this design leaves a design based on HTTP/2 as a future work and focuses on ALTO updates on HTTP/1.x and [SSE]. " I am wondering whether we can fill the gap described in RFC8895 section 3.3 on Multiplexing and Server PUSH:HTTP/2, how server push in HTTP/2 can be used in draft-schott-alto-new-transport-push-00? How it is different from PUSH Promised proposed in draft-schott-alto-new-transport-push-00? -Qin
_______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
