diff options
| -rw-r--r-- | 01.md | 2 |
1 files changed, 1 insertions, 1 deletions
| @@ -104,7 +104,7 @@ Clients can send 3 types of messages, which must be JSON arrays, according to th | |||
| 104 | * `["REQ", <subscription_id>, <filters1>, <filters2>, ...]`, used to request events and subscribe to new updates. | 104 | * `["REQ", <subscription_id>, <filters1>, <filters2>, ...]`, used to request events and subscribe to new updates. |
| 105 | * `["CLOSE", <subscription_id>]`, used to stop previous subscriptions. | 105 | * `["CLOSE", <subscription_id>]`, used to stop previous subscriptions. |
| 106 | 106 | ||
| 107 | `<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 `<subscription_id>`s are the same string, they should be treated as different subscriptions for different connections. | 107 | `<subscription_id>` is an arbitrary, non-empty string of max length 64 chars. It represents a subscription per connection. Relays MUST manage `<subscription_id>`s independently for each WebSocket connection. `<subscription_id>`s are not guarantueed to be globally unique. |
| 108 | 108 | ||
| 109 | `<filtersX>` is a JSON object that determines what events will be sent in that subscription, it can have the following attributes: | 109 | `<filtersX>` is a JSON object that determines what events will be sent in that subscription, it can have the following attributes: |
| 110 | 110 | ||