These unique features introduce the possibility of semantically diverging copies of the same files or directories, known as "conflicts". Coda allows all servers to receive updates, allowing for a greater availability of server data in the event of network partitions, a case which AFS cannot handle. AFS uses a pessimistic replication strategy with its files, only allowing one read/write server to receive updates and all other servers acting as read-only replicas. Then it transitions back to normal connected-mode operation.Īlso different from AFS is Coda's data replication method. Upon network reconnection, the client moves to reintegration state it sends logged updates to the servers. This operating state is called disconnected operation. If the network connection is lost, the Coda client's local cache serves data from this cache and logs all updates. During normal operation, a user reads and writes to the file system normally, while the client fetches, or "hoards", all of the data the user has listed as important in the event of network disconnection.
![indexing files coda 2 indexing files coda 2](https://www.panic.com/blog/wp-content/uploads/2014/10/coda-screen-1200.jpg)
Well defined semantics of sharing, even in the presence of network failureĬoda uses a local cache to provide access to server data when the network connection is lost.Continued operation during partial network failures in server network.Security model for authentication, encryption and access control.High performance through client side persistent caching.Disconnected operation for mobile computing.Coda has many features that are desirable for network file systems, and several features not found elsewhere.