Linked Cache Invalidation
draft-nottingham-linked-cache-inv-04
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Mark Nottingham , Mike Kelly | ||
| Last updated | 2013-06-23 (Latest revision 2012-12-20) | ||
| Stream | (None) | ||
| Formats |
Expired & archived
plain text
xml
htmlized
pdfized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at:
https://www.ietf.org/archive/id/draft-nottingham-linked-cache-inv-04.txt
https://www.ietf.org/archive/id/draft-nottingham-linked-cache-inv-04.txt
Abstract
This memo defines two new link types that indicate relationships between resources in terms of cache invalidation, along with a HTTP cache-control extension that takes advantage of those relationships to use them to extend response freshness. Collectively, this is referred to as Linked Cache Invalidation (LCI).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)