diff options
| author | engn33r <engn33r@users.noreply.github.com> | 2023-01-26 00:00:00 +0000 |
|---|---|---|
| committer | engn33r <engn33r@users.noreply.github.com> | 2023-01-26 00:00:00 +0000 |
| commit | 64b132a6d1fcfe5ca6cdb7ccfa026c1fb9d8de93 (patch) | |
| tree | dd01a8e5e2bbbc665ad3f2e225abf1597d64b6df | |
| parent | 0895e5ce47d6b1a52f86ba24292a310d67902786 (diff) | |
| download | websocket-client-64b132a6d1fcfe5ca6cdb7ccfa026c1fb9d8de93.tar.gz | |
link to logic of run_forever
| -rw-r--r-- | README.md | 3 |
1 files changed, 2 insertions, 1 deletions
@@ -80,9 +80,10 @@ connection is lost if it is provided with: `run_forever` provides a variety of event-based connection controls using callbacks like `on_message` and `on_error`. -`run_forever` does not automatically reconnect if the server +`run_forever` **does not automatically reconnect** if the server closes the WebSocket gracefully (returning [a standard websocket close code](https://www.rfc-editor.org/rfc/rfc6455.html#section-7.4.1)). +[This is the logic](https://github.com/websocket-client/websocket-client/pull/838#issuecomment-1228454826) behind the decision. Customizing behavior when the server closes the WebSocket should be handled in the `on_close` callback. This example uses [rel](https://github.com/bubbleboy14/registeredeventlistener) |