pub enum FetchState {
Idle,
Pending,
Receiving,
Unanswered,
Done,
}Expand description
Fetch lifecycle states.
A fetch settles two things and settles them independently: the publisher’s answer, which arrives on the control stream, and the response stream that carries the objects. Section 3.2: “The FETCH_OK or FETCH_ERROR can come at any time relative to object delivery. The publisher MAY send Objects in response to a FETCH before the FETCH_OK message is sent, but the FETCH_OK MUST NOT be sent until the publisher knows whether Largest Object is within the requested range.” So the fetch is over when both have settled, in whichever order they settle.
Variants§
Idle
Initial state before any FETCH message is sent.
Pending
FETCH has been sent; the answer is owed and the response stream has not ended.
Receiving
FETCH_OK received; data is being received on the stream.
Unanswered
The response stream has ended and the answer is still owed.
Done
Fetch has ended (error, cancel, FIN, or reset).