fix/history-rpc (#191)

* Update waku-store.md

* Update wordlist.txt

* Update specs/waku/v2/waku-store.md

Co-authored-by: Oskar Thorén <ot@oskarthoren.com>

* Update waku-store.md

Co-authored-by: Oskar Thorén <ot@oskarthoren.com>
This commit is contained in:
Dean Eigenmann 2020-09-28 05:04:58 +02:00 committed by GitHub
parent 88b851678a
commit f9ddafd3e8
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 17 additions and 4 deletions

View File

@ -1,6 +1,6 @@
---
title: Waku
version: 2.0.0-alpha5
version: 2.0.0-alpha6
status: Raw
authors: Oskar Thorén <oskar@status.im>, Dean Eigenmann <dean@status.im>
---
@ -16,7 +16,7 @@ authors: Oskar Thorén <oskar@status.im>, Dean Eigenmann <dean@status.im>
`WakuStore` is a protocol to enable querying of messages received through relay protocol and stored by other nodes.
**Protocol identifier***: `/vac/waku/store/2.0.0-alpha5`
**Protocol identifier***: `/vac/waku/store/2.0.0-alpha6`
# Wire Specification
@ -26,16 +26,28 @@ Peers communicate with each other using a request / response API. The messages s
```protobuf
message HistoryQuery {
string uuid = 1;
repeated string topics = 2;
}
message HistoryResponse {
string uuid = 1;
repeated WakuMessage messages = 2;
}
message HistoryRPC {
string request_id = 1;
HistoryQuery query = 2;
HistoryResponse response = 3;
}
```
##### HistoryRPC
A node MUST send all History messages (`HistoryQuery`, `HistoryResponse`) wrapped inside a
`HistoryRPC`. This allows the node handler to determine how to handle a message as the Waku
Filter protocol is not a request response based protocol but instead a push based system.
The `request_id` MUST be a uniquely generated string.
##### HistoryQuery
RPC call to query historical messages.

View File

@ -65,6 +65,7 @@ historyQuery
HistoryQuery
historyResponse
HistoryResponse
HistoryRPC
html
http
https