pub struct DirectMultipartContentClaim {
pub size_bytes: u64,
pub crc64nvme: String,
}Expand description
What a direct_multipart client says about the object it finished
writing, supplied at completion rather than at begin.
The claim arrives last because that is the only place a one-pass uploader can produce it: a client that had to declare the length and digest up front would have to read its payload twice, and a client reading from a pipe could not start at all. Nothing is lost by waiting — the claim was never trusted, only verified, and verification happens at completion either way.
The digest is CRC-64/NVME rather than SHA-256 because that is the checksum an S3-compatible provider computes over a multipart object: it is the only full-object evidence the provider will ever be able to show back, so it is the only thing worth claiming at all.
Fields§
§size_bytes: u64Complete byte length the client wrote across every part.
crc64nvme: StringCRC-64/NVME over the complete assembled payload, lowercase hex.
Trait Implementations§
Source§impl Clone for DirectMultipartContentClaim
impl Clone for DirectMultipartContentClaim
Source§fn clone(&self) -> DirectMultipartContentClaim
fn clone(&self) -> DirectMultipartContentClaim
1.0.0 (const: unstable) · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more