Expand description
Core storage service and configuration.
StorageService is the main entry point for storing and retrieving
objects. Each operation runs in a separate tokio task for panic isolation.
Callers supply an access timestamp, normally the HTTP request start time. It stays fixed across admission, backend calls, and TTI calculations. Initial creation and expiry are already resolved in the supplied metadata. Background renewals retain the read-derived deadline but check liveness at worker start.
See the crate-level documentation for full architecture details.
Structs§
- Storage
Service - Asynchronous storage service wrapping a single
Backend.
Constants§
- DEFAULT_
BACKGROUND_ QUEUE_ LIMIT - Default number of TTI renewals that may wait for background processing.
- DEFAULT_
CONCURRENCY_ LIMIT - Default concurrency limit for
StorageService.
Type Aliases§
- Delete
Response - Service response for
StorageService::delete_object. - GetResponse
- Service response for
StorageService::get_object. - Insert
Response - Service response for
StorageService::insert_object. - Metadata
Response - Service response for
StorageService::get_metadata.