Currently, even if the connection's ws pipe breaks or the heartbeat is otherwise failing, it will run forever in the background and spit out error traces (you can easily test this just by toggling off ethernet/wifi until the websocket heartbeat times-out, at which point it's fully broken).
It would be nice to handle this error either with a state that unambiguously marks the Connection as "broken" and unusable, and/or potentially implement an automatic reconnect. Similarly, handling the disconnect / logoff events from Steam would be great for this kind of automatic reconnect feature.
Currently, even if the connection's ws pipe breaks or the heartbeat is otherwise failing, it will run forever in the background and spit out error traces (you can easily test this just by toggling off ethernet/wifi until the websocket heartbeat times-out, at which point it's fully broken).
It would be nice to handle this error either with a state that unambiguously marks the Connection as "broken" and unusable, and/or potentially implement an automatic reconnect. Similarly, handling the
disconnect
/ logoff events from Steam would be great for this kind of automatic reconnect feature.