New Feature : Add MessageType property for Type of Message missing in server message #137
Description
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.