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
I think there's a mistake here. If isRawBytes is checked, the eventMessageHandle must handle all bytes, not slices it. Right?
Because I refer to this file at server side, and see if isRawBytes true, all bytes will be copied and dispatch a streaming event.
By the way can you explain a bit about isRawBytes. I understand that isRawBytes is used to check if the binary message is generated by ezyfox or not. If the message is generated manually, isRawBytes true, otherwise it false. Do I understand correctly? And can the manually generated binary message be false in this test method?
The text was updated successfully, but these errors were encountered:
I think there's a mistake here. If isRawBytes is checked, the eventMessageHandle must handle all bytes, not slices it. Right?
Because I refer to this file at server side, and see if isRawBytes true, all bytes will be copied and dispatch a streaming event.
By the way can you explain a bit about isRawBytes. I understand that isRawBytes is used to check if the binary message is generated by ezyfox or not. If the message is generated manually, isRawBytes true, otherwise it false. Do I understand correctly? And can the manually generated binary message be false in this test method?
The text was updated successfully, but these errors were encountered: