vacp2p
/
rfc
mirror of https://github.com/vacp2p/rfc.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

clarifies the relation bw contentTopic and topics

This commit is contained in:
Sanaz 2021-04-06 16:39:56 -07:00
parent 608b04ac45
commit eb159a8e93
No known key found for this signature in database
GPG Key ID: 0B5ACFC518E67998
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/docs/rfcs/13/README.md
View File

@ -85,7 +85,7 @@ To perform pagination, each `WakuMessage` stored at a node running the `WakuStor
RPC call to query historical messages.
- The `topics` field MUST indicate the list of topics to query.
- The `topics` field MUST indicate the list of topics to query. The items in this list correspond to the `contentTopic` of the queried Waku messages.
- `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.