pub enum UploadProgress {
Incomplete {
offset: u64,
},
Complete,
}Expand description
How far a resumable upload has progressed.
Both a chunk write and an offset query can observe that an upload is complete, so both
operations have the same two outcomes. Completion is relative to the backend handling the
operation: it means the session is terminal and the object is available through that backend’s
normal read methods. A backend that composes another backend must finish its own publication
work before returning UploadProgress::Complete.
Variants§
Incomplete
More bytes are expected. The client continues from offset.
This offset is authoritative and may be lower than the end of the chunk that was just written: backends can persist only a prefix and discard the remainder. It must remain below the session’s total length; once every byte has landed, the backend completes the upload or returns an error instead.
Complete
The session is terminal and the object is available through the backend’s normal reads.
This is an observable status rather than a one-time event. A later offset query can return
Complete again, for example when the response to the final chunk was lost.
Trait Implementations§
Source§impl Clone for UploadProgress
impl Clone for UploadProgress
Source§fn clone(&self) -> UploadProgress
fn clone(&self) -> UploadProgress
1.0.0 (const: unstable) · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read moreimpl Copy for UploadProgress
Source§impl Debug for UploadProgress
impl Debug for UploadProgress
impl Eq for UploadProgress
Source§impl PartialEq for UploadProgress
impl PartialEq for UploadProgress
Source§fn eq(&self, other: &UploadProgress) -> bool
fn eq(&self, other: &UploadProgress) -> bool
self and other values to be equal, and is used by ==.