Lesson plan
WebNFS
YANFS (Yet Another NFS), formerly WebNFS, is an extension to the Network File System (NFS) for allowing clients to access a file system over the internet using a simplified, firewall-friendly protocol. WebNFS was developed to give Java applets and other internet enabled applications a way of accessing filesystem services over the internet. While NFS provides applications on Unix with full filesystem semantics, not all of these might be needed in a distributed, read-only web environment. Conversely, access restrictions—such as requiring the use of restricted ports for originating requests—normally used in closed environments are not usually applicable in public distributed environments. In 2007, Sun Microsystems open-sourced its WebNFS implementation. The name was subsequently changed to YANFS (Yet Another NFS) to reflect the expanded scope of the project to include a server-side implementation. YANFS/WebNFS makes use of a well known port (port 2049 on both UDP and TCP) thus avoiding the overhead and unpredictability of using the ONC RPC portmap protocol. WebNFS adds public filehandles and multicomponent lookups to the NFS protocol. WebNFS has been specified by a number of RFCs: * : WebNFS Client * : WebNFS Server * : NFS URL Scheme * : Security negotiation for WebNFS
Article summary
YANFS (Yet Another NFS), formerly WebNFS, is an extension to the Network File System (NFS) for allowing clients to access a file system over the internet using a simplified, firewall-friendly protocol. WebNFS was developed to give Java applets and other internet enabled applications a way of accessing filesystem services over the internet. While NFS provides applications on Unix with full filesystem semantics, not all of these might be needed in a distributed, read-only web environment. Conversely, access restrictions—such as requiring the use of restricted ports for originating requests—normally used in closed environments are not usually applicable in public distributed environments. In 2007, Sun Microsystems open-sourced its WebNFS implementation. The name was subsequently changed to YANFS (Yet Another NFS) to reflect the expanded scope of the project to include a server-side implementation. YANFS/WebNFS makes use of a well known port (port 2049 on both UDP and TCP) thus avoiding the overhead and unpredictability of using the ONC RPC portmap protocol. WebNFS adds public filehandles and multicomponent lookups to the NFS protocol. WebNFS has been specified by a number of RFCs: * : WebNFS Client * : WebNFS Server * : NFS URL Scheme * : Security negotiation for WebNFS
Key claims
No claims recorded.
Discussion questions
- Summarise the article in your own words. Which single claim would you verify first, and why?
- Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
- If two sources disagreed about one of these facts, what would you need in order to trust one over the other?
Bibliography
No sources recorded.
Key claims and bibliography are generated from the same tracked claims and sources as the article page.