correcting benchmark data payload format and parsing messages #2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changed
JSON.stringify
when sending the payload in thedata
field, now sending the raw objectpusher:connection_established
andclient-broadcast
handlers to parsemsg.data
correctly, whether it’s a string or an objectws.readyState === WS_OPEN
before everyws.send
inpusher:ping
event to avoid errors when the socket is closedWhy
Prior payload serialization was causing server errors (
"data field must be an array"
) and complicated client-side parsing. These updates ensure full compatibility with Reverb, AnyCable, and Soketi, allowing reliable collection of latency and throughput metrics without errors.