mirror of https://github.com/vacp2p/rfc.git
Update content/docs/rfcs/13/README.md
Co-authored-by: Oskar Thorén <ot@oskarthoren.com>
This commit is contained in:
parent
52d5701678
commit
9adb15335c
|
@ -86,7 +86,7 @@ To perform pagination, each `WakuMessage` stored at a node running the `WakuStor
|
|||
RPC call to query historical messages.
|
||||
|
||||
- The `contentTopics` field MUST indicate the list of content topics to query.
|
||||
The items in this list correspond to the `contentTopic` of the queried Waku messages (see [14/WAKU-MESSAGE](../14)).
|
||||
The items in this list correspond to the `contentTopic` of the queried Waku messages (see [14/WAKU-MESSAGE](/spec/14)).
|
||||
- `PagingInfo` holds the information required for pagination. Its `pageSize` field indicates the number of `WakuMessage`s to be included in the corresponding `HistoryResponse`. If the `pageSize` is zero then no pagination is required. If the `pageSize` exceeds a threshold then the threshold value shall be used instead. In the forward pagination request, the `messages` field of the `HistoryResponse` shall contain at maximum the `pageSize` amount of waku messages whose `Index` values are larger than the given `cursor` (and vise versa for the backward pagination). Note that the `cursor` of a `HistoryQuery` may be empty (e.g., for the initial query), as such, and depending on whether the `direction` is `BACKWARD` or `FORWARD` the last or the first `pageSize` waku messages shall be returned, respectively.
|
||||
The queried node MUST sort the `WakuMessage`s based on their `Index`, where the `receivedTime` constitutes the most significant part and the `digest` comes next, and then perform pagination on the sorted result. As such, the retrieved page contains an ordered list of `WakuMessage`s from the oldest message to the most recent one.
|
||||
|
||||
|
|
Loading…
Reference in New Issue