Connected: An Internet Encyclopedia
RFC 1813 - 4. Implementation issues

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1813
Prev: 3.3.21 Procedure 21: COMMIT - Commit cached data on a server to stable storage
Next: 4.1 Multiple version support

### 4. Implementation issues

The NFS version 3 protocol was designed to allow different operating systems to share files. However, since it was designed in a UNIX environment, many operations have semantics similar to the operations of the UNIX file system. This section discusses some of the general implementation-specific details and semantic issues. Procedure descriptions have implementation comments specific to that procedure.

A number of papers have been written describing issues encountered when constructing an NFS version 2 protocol implementation. The best overview paper is still [Sandberg]. [Israel], [Macklem], and [Pawlowski] describe other implementations. [X/OpenNFS] provides a complete description of the NFS version 2 protocol and supporting protocols, as well as a discussion on implementation issues and procedure and error semantics. Many of the issues encountered when constructing an NFS version 2 protocol implementation will be encountered when constructing an NFS version 3 protocol implementation.

4.1 Multiple version support
4.2 Server/client relationship
4.3 Path name interpretation
4.4 Permission issues
4.5 Duplicate request cache
4.6 File name component handling
4.7 Synchronous modifying operations
4.8 Stable storage
4.9 Lookups and name resolution
4.10 Adaptive retransmission
4.11 Caching policies
4.12 Stable versus unstable writes
4.13 32 bit clients/servers and 64 bit clients/servers

Next: 4.1 Multiple version support

Connected: An Internet Encyclopedia
RFC 1813 - 4. Implementation issues