NFS Services Administrator's Guide

Configuring and Administering NFS Services
Configuring and Administering an NFS Server
Chapter 2 69
Figure 2-2 WebNFS Session
Figure 2-2 depicts the following steps:
1. An NFS client uses a LOOKUP request with a PUBLIC file handle to
access the foo/index.html file. The NFS client bypasses the
portmapper service and contacts the server on port 2049 (the default
port).
2. The NFS server responds with the file handle for the
foo/index.html file.
3. The NFS client sends a READ request to the server.
4. The NFS server responds with the data.
Removing the additional overhead of the PORTMAP and MOUNT
protocols reduces the binding time between the client and the server. The
WebNFS protocol reduces the number of over-the-wire requests and
makes traversing firewalls easier.
WebNFS offers no support for locking files across mounted filesystems.
Hence, multiple clients cannot synchronize their locking calls across
WebNFS mounted filesystems.