How does the file management work?
The convention here is to separate access to disk-like data storage into three layers: • the filesystem layer: in charge of initialization and management of filesystem-related operations for a given filesystem type, including the copy, move, deletion of files and directories through an instance of a Ceylan::System::FileSystemManager child class • the directory layer: in charge of directory management, to perform for example directory listing, for a given filesystem type, through an instance of a Ceylan::System::Directory child class • the file layer: in charge of file management, to create or open them, and to read of write data in files, through a factory or an instance of a Ceylan::System::File child class These three layers have been defined in an abstract level (FileSystemManager / Directory / File), meant to be fully defined for each actual filesystem configuration available: • for standard filesystem abstractions, i.e. the ones provided by most computers, including UNIX and Windo
Related Questions
- Why is there no install.exe file on the current documentation CD (August SP12) to install Library Reader for Windows (the tool to view the books and the book shelves from the CD)?
- Sometimes YouTube Downloader gets the correct file name and sometimes its generic "video.mp4". Whats going on?
- How does the file management work?