nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-09-18 19:23:44 +00:00
Code Issues Packages Projects Releases Wiki Activity

Explicitly state that the subscription_id is treated per connection

Browse Source
This commit is contained in:
Yoji Shidara 2023-07-13 14:14:36 +09:00 committed by fiatjaf_
parent 1889ac792b
commit 0b08cf545b
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
01.md
View File

@ -55,7 +55,7 @@ Clients can send 3 types of messages, which must be JSON arrays, according to th
* `["REQ", <subscription_id>, <filters JSON>...]`, used to request events and subscribe to new updates.
* `["CLOSE", <subscription_id>]`, used to stop previous subscriptions.
`<subscription_id>` is an arbitrary, non-empty string of max length 64 chars, that should be used to represent a subscription.
`<subscription_id>` is an arbitrary, non-empty string of max length 64 chars, that should be used to represent a subscription. Relays should manage `<subscription_id>`s independently for each WebSocket connection; even if `<subscrption_id>`s are the same string, they should be treated as different subscriptions for different connections.
`<filters>` is a JSON object that determines what events will be sent in that subscription, it can have the following attributes: