This reverts commit c719c8492f9cdbb4680d3f1dfa8270b0dc2001c4.
@vividvilla
This commit was added under the assumption that on abnormal closure, websocket client uses the same tcp connection. Ticker server has max tokens per connection. In case of abnormal closure and if the client uses the same connection to reconnect, the server will throw max tokens exceeded error. Looks like that is not the case always. Reverting this hacky commit and changing on the server.
This reverts commit c719c8492f9cdbb4680d3f1dfa8270b0dc2001c4. @vividvilla
This commit was added under the assumption that on abnormal closure, websocket client uses the same tcp connection. Ticker server has max tokens per connection. In case of abnormal closure and if the client uses the same connection to reconnect, the server will throw max tokens exceeded error. Looks like that is not the case always. Reverting this hacky commit and changing on the server.