Struct OffsetReader 

pub struct OffsetReader<R> { /* private fields */ }

Wraps a RangeReader so every access is shifted by base bytes: a .rete that starts at byte base of the backing resource — e.g. behind an HTML shell in a polyglot file that is both a web page and a graph — reads exactly as if it began at offset 0, lazily, touching only the .rete bytes a query needs and never the prefix. Pair with detect_polyglot_base to find base.

Implementations

impl<R> OffsetReader<R>

pub fn new(inner: R, base: u64) -> OffsetReader<R>

pub fn base(&self) -> u64

pub fn into_inner(self) -> R

Trait Implementations

impl<R> RangeReader for OffsetReader<R>

where R: RangeReader,

fn len(&self) -> u64

Total resource length in bytes.

fn read_at(&self, offset: u64, len: u64) -> Result<Vec<u8>, Error>

Read len bytes starting at offset. Implementations should error on an out-of-bounds range rather than truncating.

fn read_many(&self, ranges: &[(u64, u64)]) -> Result<Vec<Vec<u8>>, Error>

Read several (offset, len) ranges, returning each range’s bytes in request order. These ranges are independent, so a reader whose backing store is high-latency but parallelizable (an HTTP client) overrides this to issue the reads concurrently — turning N round trips into ~N/P. The default fetches them sequentially. Any range failing fails the batch.

fn concurrency(&self) -> usize

How many ranges this reader can usefully have in flight at once — the planner’s hint for probe-vs-scan and batch-size decisions (a phone’s serial sync-XHR reader reports 1; the CLI’s threaded HTTP client and the browser’s concurrent-fetch variants report their fan-out). Purely advisory: correctness never depends on it. Defaults to 1 (sequential).

fn is_empty(&self) -> bool

True when the resource is empty.