Abstract
The name space and data concerns within the AFS world create a unique set of problems when interfacing with the Windows file system API. In particular, how relative and absolute symbolic links, mount points, component substitutions and generally convoluted name space topologies are handled within a Windows file system implementation. The management of data coherency across distributed, dissimilar clients involving server side notification introduces yet more complexity in an already complex world.
Learning Objectives
How to handle the nuances of the Windows infrastructure from the outside
Keeping metadata and data coherent within a distributed world involving Windows
Understanding the intricacies of the AFS topology
How the AFS paradigm can be mapped into the Windows world