Emery Hemingway
a635873568
Replace the I/O response handler that is passed to the VFS at construction with an object that is dynamically attached to handles. This object shall also accept read-ready notifications, and plugins are encouraged to keep handles awaiting ready-ready notifications separate from handles that await I/O progress. Replace the use of handle lists in plugins with handle queues, this makes the code easier to understand and the ordering of notifications to the application more explicit. These changes replace the use of the Post_signal_hook from all VFS plugins, applications must assume that read-ready and I/O notifications occur during I/O signal dispatch and use an Io_progress_handler at its entrypoints to defer response until after signal dispatching. Fix #3257 |
||
|---|---|---|
| .. | ||
| main.cc | ||
| README | ||
| target.mk | ||
The fs_tool component performs a sequence of file operations on a locally configured VFS. The file operations are given the configuration as follows: ! <config exit="yes"> ! <vfs> ! ... ! </vfs> ! <remove-file path="/path/to/file" /> ! </config> The 'exit="yes"' attribute instructs the component to exit after completing the sequence. Otherwise, the component keeps responding to configuration changes by executing the operations found in the updated configurations.