diff options
| author | fiatjaf <fiatjaf@gmail.com> | 2023-12-02 15:05:59 -0300 |
|---|---|---|
| committer | fiatjaf <fiatjaf@gmail.com> | 2023-12-02 15:05:59 -0300 |
| commit | 0ba4589550858bb86ed533f90054bfc642aa5350 (patch) | |
| tree | 5aea6e70808a699bb69f1816ca2607c66a683b12 | |
| parent | 131fcab95c49a828a216145b542e05e9bfbf0381 (diff) | |
remove websocket status code meaning as it is replaced by the CLOSED message.
| -rw-r--r-- | 01.md | 4 |
1 files changed, 0 insertions, 4 deletions
| @@ -96,10 +96,6 @@ These are just conventions and relay implementations may differ. | |||
| 96 | 96 | ||
| 97 | Relays expose a websocket endpoint to which clients can connect. Clients SHOULD open a single websocket connection to each relay and use it for all their subscriptions. Relays MAY limit number of connections from specific IP/client/etc. | 97 | Relays expose a websocket endpoint to which clients can connect. Clients SHOULD open a single websocket connection to each relay and use it for all their subscriptions. Relays MAY limit number of connections from specific IP/client/etc. |
| 98 | 98 | ||
| 99 | ### Meaning of WebSocket status codes | ||
| 100 | |||
| 101 | - When a websocket is closed by the relay with a status code `4000` that means the client shouldn't try to connect again. | ||
| 102 | |||
| 103 | ### From client to relay: sending events and creating subscriptions | 99 | ### From client to relay: sending events and creating subscriptions |
| 104 | 100 | ||
| 105 | Clients can send 3 types of messages, which must be JSON arrays, according to the following patterns: | 101 | Clients can send 3 types of messages, which must be JSON arrays, according to the following patterns: |