Question: What is Macfusion's network file systems based on?

Context articles: Macfusion
File Allocation Table
SSHFS
Fork (file system)
Fstab
Semantic file system
Virtual file system
Global file system
MAC times
Hard link

Macfusion is an open-source network file-system client, based on FUSE, CurlFtpFS and SSHFS.
File Allocation Table (FAT) is a computer file system architecture and a family of industry-standard file systems utilizing it.
 The FAT file system is a legacy file system which is simple and robust.
 It offers good performance even in lightweight implementations, but cannot deliver the same performance, reliability and scalability as some modern file systems.
 It is, however, supported for compatibility reasons by nearly all currently developed operating systems for personal computers and many mobile devices and embedded systems, and thus is a well-suited format for data exchange between computers and devices of almost any type and age from 1981 up to the present.
In computing, SSHFS (SSH Filesystem) is a filesystem client to mount and interact with directories and files located on a remote server or workstation over a normal ssh connection.
 The client interacts with the remote file system via the SSH File Transfer Protocol (SFTP), a network protocol providing file access, file transfer, and file management functionality over any reliable data stream that was designed as an extension of the Secure Shell protocol (SSH) version 2.0.
In a computer file system, a fork is a set of data associated with a file system object.
 File systems without forks only allow a single such set of data for the contents, while file systems with forks allow multiple such contents.
 Every non-empty file must have at least one fork, often of default type, and depending on the file system, a file may have one or more other associated forks, which in turn may contain primary data integral to the file, or just metadata.
 Unlike "extended attributes", a similar file system feature which is typically of fixed size, forks can be of variable size, possibly even larger than the file's primary data fork.
 The size of a file is the sum of the sizes of each fork.
 Forks are also known as streams, since they are of variable size (unlike fixed size metadata), but this differs from .
The fstab (or "file systems table") file is a system configuration file commonly found at codice_1 on Unix and Unix-like computer systems.
 In Linux it is part of the util-linux package.
 The fstab file typically lists all available disk partitions and other types of file systems and data sources that are not necessarily disk-based, and indicates how they are to be initialized or otherwise integrated into the larger file system structure.
Semantic file systems are file systems used for information persistence which structure the data according to their semantics and intent, rather than the location as with current file systems.
 It allows the data to be addressed by their content (associative access).
 Traditional hierarchical file-systems tend to impose a burden, for example when a sub-directory layout is contradicting a user's perception of where files would be stored.
 Having a tag-based interface alleviates this hierarchy problem and enables users to query for data in an intuitive fashion.
A virtual file system (VFS) or virtual filesystem switch is an abstraction layer on top of a more concrete file system.
 The purpose of a VFS is to allow client applications to access different types of concrete file systems in a uniform way.
 A VFS can, for example, be used to access local and network storage devices transparently without the client application noticing the difference.
 It can be used to bridge the differences in Windows, classic Mac OS/macOS and Unix filesystems, so that applications can access files on local file systems of those types without having to know what type of file system they are accessing.
In computer science, global file system has historically referred to a distributed virtual name space built on a set of local file systems to provide transparent access to multiple, potentially distributed, systems.
 These global file systems had the same properties such as blocking interface, no buffering etc. but guaranteed that the same path name corresponds to the same object on all computers deploying the filesystem.
 Also called distributed file systems these file systems rely on redirection to distributed systems, therefore latency and scalability can affect file access depending on where the target systems reside.
MAC times are pieces of file system metadata which record when certain events pertaining to a computer file occurred most recently.
 The events are usually described as "modification" (the data in the file was modified), "access" (some part of the file was read), and "metadata change" (the file's permissions or ownership were modified), although the acronym is derived from the "mtime", "atime", and "ctime" structures maintained by Unix file systems.
 Windows file systems do not update ctime when a file's metadata is changed , instead using the field to record the time when a file was first created, known as "creation time" or "birth time".
 Some other systems also record birth times for files, but there is no standard name for this metadata; ZFS, for example, stores birth time in a field called "crtime".
 MAC times are commonly used in computer forensics.
 The name Mactime was originally coined by Dan Farmer, who wrote a tool with the same name.
In computing, a hard link is a directory entry that associates a name with a file on a file system.
 All directory-based file systems must have (at least) one hard link giving the original name for each file.
 The term “"hard link"” is usually only used in file systems that allow more than one hard link for the same file.