Expand description
Provider-neutral object storage, direct access, and verified upload workflows.
Structs§
- Issue
Object Upload - Application-authorized request for one direct object upload.
- Issued
Object Upload - Split result that prevents the bearer request from becoming trusted state by
accident. Return only
Self::grantto the client and retainSelf::pendingon the server. - Managed
Object Storage Plugin - Object-storage plugin with the direct-upload and metadata lifecycle installed.
- Memory
Object Store - Object
Access Service - Object
Head - Metadata returned without loading an object’s bytes into application memory.
- Object
Key - Object
Metadata - Object
Metadata Service - Typed metadata service injected by a managed object-storage plugin.
- Object
Storage Plugin - Object
Store Service - Object
Upload Grant - Client-facing bearer capability. Send this value to the authorized client, but never persist or log it as the trusted upload record.
- Object
Upload Policy - Closed upload policy owned by the application composition root.
- Object
Upload Service - Issues unique direct-upload capabilities and verifies their provider metadata.
- Pending
Object Upload - Trusted server-side record for one issued upload capability.
- Presign
GetObject - Presign
PutObject - Presigned
Object Request - Browser- or client-usable request produced by a provider adapter such as S3.
- PutObject
- Sign
Object Upload - Exact provider request for one checksummed direct upload.
- Stored
Object - Verified
Object Upload - Metadata accepted after the provider confirms the issued upload contract.
Enums§
- Object
Store Error - Object
Upload Error - Presigned
Method - HTTP method required by a signed direct-object request.
Traits§
- Object
Access Signer - Provider adapter for direct upload and download URLs.
- Object
Metadata Reader - Provider port for an inexpensive metadata lookup such as S3
HeadObject. - Object
Store - Object
Upload Signer - Provider adapter that can bind an upload capability to exact bytes.