Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

About handleBinaryMessage #17

Open
tiennm99 opened this issue Nov 26, 2022 · 0 comments
Open

About handleBinaryMessage #17

tiennm99 opened this issue Nov 26, 2022 · 0 comments

Comments

@tiennm99
Copy link

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant