Movatterモバイル変換

A new Request for Comments is now available in online RFC libraries.RFC 3229        Title:      Delta encoding in HTTP        Author(s):  J. Mogul, B. Krishnamurthy, F. Douglis,                    A. Feldmann, Y. Goland, A. van Hoff,                    D. Hellerstein        Status:     Standards Track        Date:       January 2002        Mailbox:    JeffMogul@acm.org, bala@research.att.com,                    douglis@research.att.com, anja@cs.uni-sb.de,                    yaron@goland.org, avh@marimba.com,                    danielh@crosslink.net        Pages:      49        Characters: 111953        Updates/Obsoletes/SeeAlso:  None        I-D Tag:draft-mogul-http-delta-10.txt        URL:ftp://ftp.rfc-editor.org/in-notes/rfc3229.txtThis document describes how delta encoding can be supported as acompatible extension to HTTP/1.1.Many HTTP (Hypertext Transport Protocol) requests cause the retrievalof slightly modified instances of resources for which the clientalready has a cache entry.  Research has shown that such modifyingupdates are frequent, and that the modifications are typically muchsmaller than the actual entity.  In such cases, HTTP would make moreefficient use of network bandwidth if it could transfer a minimaldescription of the changes, rather than the entire new instance of theresource.  This is called "delta encoding."This is now a Proposed Standard Protocol.This document specifies an Internet standards track protocol forthe Internet community, and requests discussion and suggestionsfor improvements.  Please refer to the current edition of the"Internet Official Protocol Standards" (STD 1) for thestandardization state and status of this protocol.  Distributionof this memo is unlimited.This announcement is sent to the IETF list and the RFC-DIST list.Requests to be added to or deleted from the IETF distribution listshould be sent to IETF-REQUEST@IETF.ORG.  Requests to beadded to or deleted from the RFC-DIST distribution list shouldbe sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.Details on obtaining RFCs via FTP or EMAIL may be obtained by sendingan EMAIL message to rfc-info@RFC-EDITOR.ORG with the message bodyhelp: ways_to_get_rfcs.  For example:        To: rfc-info@RFC-EDITOR.ORG        Subject: getting rfcs        help: ways_to_get_rfcsRequests for special distribution should be addressed to either theauthor of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unlessspecifically noted otherwise on the RFC itself, all RFCs are forunlimited distribution.echoSubmissions for Requests for Comments should be sent toRFC-EDITOR@RFC-EDITOR.ORG.  Please consultRFC 2223, Instructions to RFCAuthors, for further information.

• Info
• Contents
• Prefs