You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current implementation doesn’t check the pong
always sends a bytes_len of 64.
These seem like two separate issues - the spec seems to be referencing checking that the size of the received pong is the size that we expect (which we should be doing?). As for the sending side, we should probably stop setting it to 64 and wasting bytes and always set it to 0.
The current implementation doesn’t check the pong and always sends a bytes_len of 64.
What is the value of implementing this feature? Should we document anywhere that we are intentionally doing nothing?
The text was updated successfully, but these errors were encountered: