Closed 3vcloud closed 2 months ago
Client sometimes caches the 'ping' text and sends it later with another message, like 'pingping', or 'ping{json}'. This breaks the parsing on the server.
We could rely on the ping
pong
message types which should be handled internally with no need for manual handling
I tried to replicate the issue through here, but I can't replicate it https://websocketking.com/
The server handles message framing just fine. It's the client the bundles them
Send the message with full_list
set to true
and the server will return you the entire list of party searches in the response
Works on both live-feed
and update
urls
Add ping handling to the bot websocket, but also add a handler for something like "parties" for both websockets that executes the
GetAllPartySearches
logic and sends it back