This allows the developer to react to any changes in the websocket connection or handle any errors received from hyperliquid. Example: Dynamically closing and opening the websocket upon errors.
Previously the errors would just get logged and the thread would continue running.
Possible an AtomicBool to start and stop the sender thread too?
Fixes issue #45
This allows the developer to react to any changes in the websocket connection or handle any errors received from hyperliquid. Example: Dynamically closing and opening the websocket upon errors.
Previously the errors would just get logged and the thread would continue running.
Possible an AtomicBool to start and stop the sender thread too?