Resource Maps
draft-eriksson-http-resource-map-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Goran Eriksson , Christer Holmberg , Zaheduzzaman Sarker , Julian Reschke | ||
| Last updated | 2017-05-04 (Latest revision 2016-10-31) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| 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 is available in these formats:
Abstract
When the 'out-of-band' content coding ('OOB') is used for delivering a number of resources from a primary server via a secondary server, the additional round trips for OOB responses and load on the primary server can be a significant nuisance. In such situations, it is useful for the primary server to be able to provide the client with OOB response information for several resources in one go anticipating future client requests. This document describes a format for providing the client with the information, called a resource map, and how the resource map could be delivered to a client.
Authors
Goran Eriksson
Christer Holmberg
Zaheduzzaman Sarker
Julian Reschke
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)