Expand description
Filesystem access shaped so that latency optimisation survives a backend swap.
The operations are batch-first on purpose. A per-path interface — stat(p),
read(p) — forces O(N) round trips no matter which backend implements it, so
the abstraction would defeat the invariant it sits beneath. A single read is
the n=1 case of read_batch, not the other way round.
Modules§
- sftp
- Concurrent SFTP access over a single stream.
Structs§
- Entry
- Range
Req - One byte range of one file.
- Refused
- A refusal from the remote, carrying the reason it gave.
Traits§
Functions§
- is_
absent - Did this failure mean “there is nothing there”, as opposed to anything else at all?