A publisher sends a FETCH_OK control message in response to successful fetches. A 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 end group and object are known.
FETCH_OK Message {
Type (i) = 0x18,
Length (i),
Request ID (i),
Group Order (8),
End Of Track (8),
End Location (Location),
Number of Parameters (i),
Subscribe Parameters (..) ...
}
-
Request ID: The Request ID of the FETCH this message is replying to Section 8.7.
-
Group Order: Indicates the fetch will be delivered in Ascending (0x1) or Descending (0x2) order by group. See Section 6. Values of 0x0 and those larger than 0x2 are a protocol error.
-
End Of Track: 1 if all objects have been published on this track, so the End Group ID and Object Id indicate the last Object in the track, 0 if not.
-
End Location: The largest object covered by the FETCH response. This is the minimum of the {End Group,End Object} specified in FETCH and the largest known {group,object}. If the relay is currently subscribed to the track, the largest known {group,object} at the relay is used. For tracks with a requested end larger than what is cached without an active subscription, the relay makes an upstream request in order to satisfy the FETCH.
-
Subscribe Parameters: The parameters are defined in Section 8.2.1.