Connected: An Internet Encyclopedia
RFC 1813 - 4.9 Lookups and name resolution

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1813
Up: 4. Implementation issues
Prev: 4.8 Stable storage
Next: 4.10 Adaptive retransmission

### 4.9 Lookups and name resolution

A common objection to the NFS version 3 protocol is the philosophy of component-by-component LOOKUP by the client in resolving a name. The objection is that this is inefficient, as latencies for component-by-component LOOKUP would be unbearable.

Implementation practice solves this issue. A name cache, providing component to file-handle mapping, is kept on the client to short circuit actual LOOKUP invocations over the wire. The cache is subject to cache timeout parameters that bound attributes.

Next: 4.10 Adaptive retransmission

Connected: An Internet Encyclopedia
RFC 1813 - 4.9 Lookups and name resolution