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

New Feature : Add MessageType property for Type of Message missing in server message #137

Open
frogeater opened this issue Sep 5, 2023 · 0 comments
Labels
good first issue Good for newcomers

Comments

@frogeater
Copy link

One of the websocket servers I'm accessing doesn't seem to provide a type for the messages it sends.
WebsocketClient therefore supplies the message in binary.
However, I know that the server sends json messages in UTF8.
This isn't a problem because I know that the messages are json UTF8 and I can convert the message to text.
WebsocketClient allows you to indicate the encoding in the MessageEncoding property, but does not allow you to indicate the message type, which means that you can't use message-to-text conversion in this case.
To correct the server's lack of type, a 'MessageType' property that can be used by default in case the server "forgets" would be a bonus.

@Marfusios Marfusios added the good first issue Good for newcomers label Sep 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants