- From: Mark Nottingham <mnot@mnot.net>
- Date: Thu, 30 Jan 2014 11:07:12 +1100
- To: Roberto Peon <grmocg@gmail.com>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
So, we've always talked about pushing into the cache; presumably, if you push something that's no-cache, it has a special state that allows it to be used once / within a browsing context, but it's still being pushed into the cache (indeed, the HTTP caching model already talks about caching things that are no-cache). On 30 Jan 2014, at 11:05 am, Roberto Peon <grmocg@gmail.com> wrote: > No, I think that would add to confusion, especially if we ever change the spec to allow push of no-cache resources, etc. > > On Jan 29, 2014 4:00 PM, "Mark Nottingham" <mnot@mnot.net> wrote: > I've noticed some confusion when I talk to people about server push, because it's not clear whether the server is being pushed to or from, and it doesn't make clear what's really happening. > > What do people think about calling it "cache push" instead? To me, it gets to the heart of what's happening more clearly. > > Cheers, > > > -- > Mark Nottingham http://www.mnot.net/ > > > > -- Mark Nottingham http://www.mnot.net/
Received on Thursday, 30 January 2014 00:07:41 UTC