diff options
| author | Yoji Shidara <dara@shidara.net> | 2023-07-13 14:14:36 +0900 |
|---|---|---|
| committer | fiatjaf_ <fiatjaf@gmail.com> | 2023-07-13 07:08:26 -0300 |
| commit | 0b08cf545b50b4799000e90aa4c5ada2cb73ca62 (patch) | |
| tree | f52ae2d7276f5b377dc8b7b015b8c2fc67b3746a /01.md | |
| parent | 1889ac792b7119ba9dc41fd4e904445ad1d9c6b5 (diff) | |
Explicitly state that the `subscription_id` is treated per connection
Diffstat (limited to '01.md')
| -rw-r--r-- | 01.md | 2 |
1 files changed, 1 insertions, 1 deletions
| @@ -55,7 +55,7 @@ Clients can send 3 types of messages, which must be JSON arrays, according to th | |||
| 55 | * `["REQ", <subscription_id>, <filters JSON>...]`, used to request events and subscribe to new updates. | 55 | * `["REQ", <subscription_id>, <filters JSON>...]`, used to request events and subscribe to new updates. |
| 56 | * `["CLOSE", <subscription_id>]`, used to stop previous subscriptions. | 56 | * `["CLOSE", <subscription_id>]`, used to stop previous subscriptions. |
| 57 | 57 | ||
| 58 | `<subscription_id>` is an arbitrary, non-empty string of max length 64 chars, that should be used to represent a subscription. | 58 | `<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. |
| 59 | 59 | ||
| 60 | `<filters>` is a JSON object that determines what events will be sent in that subscription, it can have the following attributes: | 60 | `<filters>` is a JSON object that determines what events will be sent in that subscription, it can have the following attributes: |
| 61 | 61 | ||