- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Fri, 8 Apr 2016 14:30:08 -0300
- To: Phil Lello <phil@dunlop-lello.uk>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
On 8 April 2016 at 13:00, Phil Lello <phil@dunlop-lello.uk> wrote: > In both a traditional desktop browser environment and server-to-server web > services, paging is often used when dealing with a set of results. To > optimise responsiveness, a server could send page 1 and push page 2. The > objective here is to tell the server when page 2 is requested by the client > so that it can prepare/push page 3. In a browser environment, this could be > implemented with client-side application logic, but DELETE seems like the > wrong action. In a server-to-server environment for a public webservice, > where there will be multiple client implementation, it seems better to > handle this with a 'push-consumed' frame at the HTTP/2 level, so a server > can try to keep pipelines full for clients without changing > application-level semantics. I don't see any way around the problem here. The consumption of the resource is not what you are looking to trigger on; that could occur long before the navigation happens. The event of interest exists at the application layer. Use an application layer mechanism.
Received on Friday, 8 April 2016 17:30:38 UTC