projects2080

WebSocketClient should propagate ConnectionClosedError after max_reconnects

3

Currently it silently just ends after max reconnects is exceeded, instead of return it should raise the ConnectionClosedError.

Give raw string bytes in socket message instead of string

15

### Is your feature request related to a problem? For very high performance websocket clients it is sometimes not desirable to automatically convert bytes to string, even if the server...