Network File System (NFS) version 4 byte range delegations
draft-myklebust-nfsv4-byte-range-delegations-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Trond Myklebust | ||
| Last updated | 2005-10-18 | ||
| 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
This document describes a set of extensions to the NFS version 4 protocol that enable the client to cache file data when caching conflicts prevent the server from handing out a file delegation. The proposed extensions enable the caching of only those specific byte ranges of data which the user application is reading or writing. As in the case of full delegations, a callback mechanism enables the server to request that the client flush cached data when a caching conflict occurs.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)