Optional
options: waku_store.CreateOptionsDo a query to a Waku Store to retrieve historical/missed messages.
The callback function takes a Promise<WakuMessage>
in input,
useful if messages needs to be decrypted and performance matters.
The order of the messages passed to the callback is as follows:
Do note that the resolution of the Promise<WakuMessage | undefined
may
break the order as it may rely on the browser decryption API, which in turn,
may have a different speed depending on the type of decryption.
If not able to reach a Waku Store peer to query, or if an error is encountered when processing the reply, or if two decoders with the same content topic are passed.
Optional
options: QueryOptionsDo a query to a Waku Store to retrieve historical/missed messages.
This is a generator, useful if you want most control on how messages are processed.
The order of the messages returned by the remote Waku node SHOULD BE as follows:
However, there is no way to guarantee the behavior of the remote node.
If not able to reach a Waku Store peer to query, or if an error is encountered when processing the reply, or if two decoders with the same content topic are passed.
Optional
options: QueryOptionsDo a query to a Waku Store to retrieve historical/missed messages.
The callback function takes a WakuMessage
in input,
messages are processed in order:
options.pageDirection
== FORWARDoptions.pageDirection
== BACKWARDThe ordering may affect performance. The ordering depends on the behavior of the remote store node. If strong ordering is needed, you may need to handle this at application level and set your own timestamps too (the WakuMessage timestamps are not certified).
If not able to reach a Waku Store peer to query, or if an error is encountered when processing the reply, or if two decoders with the same content topic are passed.
Optional
options: QueryOptionsGenerated using TypeDoc
Implements the Waku v2 Store protocol.
The Waku Store protocol can be used to retrieved historical messages.