Currently, the Distributed File subsystem provides apps with JavaScript APIs for I/O capabilities, including APIs for managing files and directories, obtaining file information, reading and writing data streams of files, and receiving URIs rather than absolute paths.
### Architecture<a name="section110mcpsimp"></a>
Currently, the Distributed File subsystem provides only local JavaScript file APIs for apps through the FileIO and File modules. The Distributed File subsystem uses LibN to abstract APIs at the NAPI layer, providing basic capabilities such as the basic type system, memory management, and general programming models for the subsystem. This subsystem depends on the engine layer of the JS application development framework to provide the capability of converting JavaScript APIs into C++ code, depends on the application framework to provide app-related directories, and depends on the GLIBC runtimes to provide I/O capabilities.
- The URIs cannot include external storage directories.
## Usage<a name="section125mcpsimp"></a>
### Available APIs<a name="section127mcpsimp"></a>
Currently, the Distributed File subsystem provides APIs for accessing local files and directories. The following table describes the API types classified by function.
<thclass="cellrowborder"valign="top"width="26.889999999999997%"id="mcps1.2.5.1.4"><pid="p129221017720"><aname="p129221017720"></a><aname="p129221017720"></a>Example API (<emid="i15670628145315"><aname="i15670628145315"></a><aname="i15670628145315"></a>Class Name</em>.<emid="i6859230125316"><aname="i6859230125316"></a><aname="i6859230125316"></a>Method Name</em>)</p>
<tdclass="cellrowborder"valign="top"width="32.25%"headers="mcps1.2.5.1.2 "><pid="p89236171124"><aname="p89236171124"></a><aname="p89236171124"></a>Creates, modifies, and accesses files, and changes file permissions based on the specified absolute paths or file descriptors.</p>
<tdclass="cellrowborder"valign="top"width="32.25%"headers="mcps1.2.5.1.2 "><pid="p109232176211"><aname="p109232176211"></a><aname="p109232176211"></a>Reads directories and determines file types based on the specified absolute paths.</p>
<tdclass="cellrowborder"valign="top"width="32.25%"headers="mcps1.2.5.1.2 "><pid="p1992314179215"><aname="p1992314179215"></a><aname="p1992314179215"></a>Collects basic statistics including the file size, access permission, and modification time based on the specified absolute paths.</p>
<tdclass="cellrowborder"valign="top"width="32.25%"headers="mcps1.2.5.1.2 "><pid="p992311171421"><aname="p992311171421"></a><aname="p992311171421"></a>Reads and writes data streams of files based on the specified absolute paths or file descriptors.</p>
<tdclass="cellrowborder"valign="top"width="32.25%"headers="mcps1.2.5.1.2 "><pid="p49237171020"><aname="p49237171020"></a><aname="p49237171020"></a>Provides a subset or a combination of the capabilities provided by the basic file, directory, and statistical APIs based on the specified URIs.</p>
<tdclass="cellrowborder"valign="top"width="47.620000000000005%"headers="mcps1.2.5.1.4 "><pid="p16896726173311"><aname="p16896726173311"></a><aname="p16896726173311"></a>Readable and writable, and can be cleared at any time. This directory is usually used for temporary downloads or caches.</p>
</td>
</tr>
<trid="row194741315193312"><tdclass="cellrowborder"valign="top"width="13.969999999999999%"headers="mcps1.2.5.1.1 "><pid="p12896142620339"><aname="p12896142620339"></a><aname="p12896142620339"></a>Private directory of an app</p>
<tdclass="cellrowborder"valign="top"width="47.620000000000005%"headers="mcps1.2.5.1.4 "><pid="p1089682623314"><aname="p1089682623314"></a><aname="p1089682623314"></a>Deleted when the app is uninstalled.</p>
<tdclass="cellrowborder"valign="top"width="47.620000000000005%"headers="mcps1.2.5.1.4 "><pid="p5897126113313"><aname="p5897126113313"></a><aname="p5897126113313"></a>Deleted when the app is uninstalled. Other apps with granted permissions can read and write files in this directory.</p>
The I/O APIs provided by the Distributed File subsystem can be classified into the following types based on the programming model:
- Synchronous programming model
APIs whose names contain **Sync** are implemented as a synchronous model. When a synchronous API is called, the calling process waits until a value is returned.
The following example opens a file stream in read-only mode, attempts to read the first 4096 bytes, converts them into a UTF-8-encoded string, and then closes the file stream:
```
import fileio from '@OHOS.distributedfile.fileio';
try {
var ss = fileio.Stream.createStreamSync("tmp", "r")
buf = new ArrayBuffer(4096)
ss.readSync(buf)
console.log(String.fromCharCode.apply(null, new Uint8Array(buf)))
ss.closeSync()
}
catch (e) {
console.log(e);
}
```
- Asynchronous programming model: Promise
In the **@OHOS.distributedfile.fileio** module, the APIs whose names do not contain **Sync** and to which a callback is not passed as their input parameter are implemented as the Promise asynchronous model. The Promise asynchronous model is one of the OHOS standard asynchronous models. When an asynchronous API using the Promise model is called, the API returns a Promise object while executing the concerned task asynchronously. The Promise object represents the asynchronous operation result. When there is more than one result, the results are returned as properties of the Promise object.
In the following example, a Promise chain is used to open a file stream in read-only mode, attempt to read the first 4096 bytes of the file, display the length of the content read, and then close the file:
```
import fileio from '@OHOS.distributedfile.fileio';
try {
let openedStream
fileio.Stream.createStream("test.txt", "r")
.then(function (ss) {
openedStream = ss;
return ss.read(new ArrayBuffer(4096))
})
.then(function (res) {
console.log(res.bytesRead);
console.log(String.fromCharCode.apply(null, new Uint8Array(res.buffer)))
return openedStream.close()
})
.then(function (undefined) {
console.log("Stream is closed")
})
.catch(function (e) {
console.log(e)
})
} catch (e) {
console.log(e)
}
```
- Asynchronous programming model: Callback
In the **@OHOS.distributedfile.fileio** module, the APIs whose names do not contain **Sync** and to which a callback is directly passed as their input parameter are implemented as the callback asynchronous model. The callback asynchronous model is also one of the OHOS standard asynchronous models. When an asynchronous API with a callback passed is called, the API executes the concerned task asynchronously and returns the execution result as the input parameters of the registered callback. The first parameter is of the **undefined** or **Error** type, indicating that the execution succeeds or fails, respectively.
The following example creates a file stream asynchronously, reads the first 4096 bytes of the file asynchronously in the callback invoked when the file stream is created, and then closes the file asynchronously in the callback invoked when the file is read:
```
import fileio from '@OHOS.distributedfile.fileio';
try {
fileio.Stream.createStream("./testdir/test_stream.txt", "r", function (err, ss) {
if (!err) {
ss.read(new ArrayBuffer(4096), {}, function (err, buf, readLen) {
if (!err) {
console.log('readLen: ' + readLen)
console.log('data: ' + String.fromCharCode.apply(null, new Uint8Array(buf)))
} else {
console.log('Cannot read from the stream ' + err)
}
ss.close(function (err) {
console.log(`Stream is ${err ? 'not' : ''}closed`)
});
})
} else {
console.log('Cannot open the stream ' + err)
}
})
} catch (e) {
console.log(e)
}
```
- Asynchronous programming model: Legacy
All APIs in the **@system.file** module are implemented as the legacy asynchronous model. When calling such an API, you need to implement three callbacks \(including **success**, **fail**, and **complete**\) to be invoked when the execution is successful, fails, or is complete, respectively. If the input parameters are correct, the API calls the **success** or **fail** callback based on whether the asynchronous task is successful after the task execution is complete, and finally calls the **complete** callback.
The following example asynchronously checks whether the file pointed to by the specified URI exists and provides three callbacks to print the check result:
The file management subsystem provides a complete file management solution for OpenHarmony. It provides secure and easy file access and comprehensive file management capabilities, including:
The file management subsystem provides a complete file management solution for OpenHarmony. It provides secure and easy-to-use file access and comprehensive file management capabilities, including:
- A sandbox to ensure the least privilege as well as application data security
- Unified management of user files and streamlined user data access and storage to ensure user data security and purity
...
...
@@ -18,10 +18,10 @@ The file management subsystem provides the file access framework, file sharing f
| File access interface| 1. Provides complete JavaScript APIs to implement basic file access capabilities.<br>2. Provides extension APIs for local files, distributed files, and cloud files.|
| Storage management | 1. Provides the data backup and restoration capability to support system and application data backup and cloning.<br>2. Provides space management capabilities such as application space clearing and statistics, and quota control.<br>3. Provides storage management capabilities such as mount operations, external card management, device management, and multi-user management.|
| User files | 1. Provides a sandbox to ensure user data security and purity.<br>2. Allows access to user data only through **medialibrary**.<br>3. Provides a unified file management framework.<br>4. Supports distributed and device-cloud capabilities.|
| Application files | 1. Provides a sandbox to ensure the least privilege as well as application data security.<br>2. Supports file sharing between apps, across devices, and in groups.<br>3. Allows applications to access distributed and cloud files as they access local files.|
| Distributed capabilities | 1. Provides basic cross-device access capabilities and supports distributed access using the same account and temporary access using different accounts.<br>2. Support device-cloud interaction irrespective of the data locations.<br>3. Supports cross-device hopping, such as application hopping and distributed clipboard.|
| Storage management | 1. Provides data backup and restore to support system and application data backup and cloning.<br>2. Provides space management capabilities such as application space clearing and statistics, and quota control.<br>3. Provides storage management capabilities such as mount operations, external card management, device management, and multi-user management.|
| User files | 1. Provides a sandbox to ensure user data security and purity.<br>2. Allows access to user data only through **mediaLibrary**.<br>3. Provides a unified file management framework.<br>4. Supports distributed and device-cloud capabilities.|
| Application files | 1. Provides a sandbox to ensure the least privilege as well as application data security.<br>2. Supports file sharing between applications, across devices, and in groups.<br>3. Allows applications to access distributed and cloud files as they access local files.|
| Distributed capabilities | 1. Provides basic cross-device access capabilities and supports distributed access using the same account and temporary access using different accounts.<br>2. Supports device-cloud interaction irrespective of the data locations.<br>3. Supports cross-device hopping, such as application hopping and distributed pasteboard.|
| Basic file system| 1. Supports local file systems such as ext4, Flash-Friendly File System (F2FS), Extensible File Allocation Table (exFAT), and New Technology File System (NTFS).<br>2. Supports network file systems such as the distributed file system and Network File System (NFS).<br>3. Provides tools related to file systems.|
