logos-messaging/pm
1
0
Fork 0
mirror of https://github.com/logos-messaging/pm.git synced 2026-01-11 02:23:09 +00:00
Code Issues Packages Projects Releases Wiki Activity

no pubsub topics

Browse Source
This commit is contained in:
fryorcraken 2025-06-04 13:00:32 +10:00
parent 2c41d007ed
commit 82de90f8e4
No known key found for this signature in database
GPG Key ID: A82ED75A8DFC50A4
3 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
FURPS/core/light_push.md
View File

@ -3,7 +3,7 @@
## Functionality
1. Enables light nodes to push messages to service nodes for relay to the network.
2. Requests service nodes to publish messages to WAKU2-RELAY pubsub-topics.
2. Requests service nodes to publish messages to WAKU2-RELAY shards.
3. Provides confirmation that a message has been received by at least one node.
4. Supports comprehensive error codes for various failure scenarios.

1
FURPS/core/waku_api.md
View File

@ -16,6 +16,7 @@
2. Disconnection detection and recovery, and other peer management matters are automatically handled.
3. Developers do not need to specify the protocols used to send and receive messages; it is deduced from the mode of operation.
4. Developers pass and receive data to the API in types native to the wrapping language.
5. By default, auto-sharding is applied, meaning developers do not need to be concerned by sharding; pubsub topics are never exposed.
## Reliability

2
draft-roadmap/improve_devex_api_twn_metrics_docs.md
View File

@ -87,6 +87,7 @@ Spec delivery not included.
- U2. Disconnection detection and recovery, and other peer management matters are automatically handled.
- U3. Developers do not need to specify the protocols used to send and receive messages; it is deduced from the mode of operation.
- U4. Developers pass and receive data to the API in types native to the wrapping language.
- U5. By default, auto-sharding is applied, meaning developers do not need to be concerned by sharding; pubsub topics are never exposed.
- R1. Sends a message using peer-to-peer reliability (service node redundancy, optional store confirmation)
- R2. Receives messages using peer-to-peer reliability (service node redundancy, periodic store query, periodic filter ping)
@ -113,6 +114,7 @@ For S3. Browser
- U2. Disconnection detection and recovery, and other peer management matters are automatically handled.
- U3. Developers do not need to specify the protocols used to send and receive messages; it is deduced from the mode of operation.
- U4. Developers pass and receive data to the API in types native to the wrapping language.
- U5. By default, auto-sharding is applied, meaning developers do not need to be concerned by sharding; pubsub topics are never exposed.
- R1. Sends a message using peer-to-peer reliability (service node redundancy, optional store confirmation)
- R2. Receives messages using peer-to-peer reliability (service node redundancy, periodic store query, periodic filter ping)