Hello, and thank you for providing WatsonWebsocket. It's a delight to use it :-)
But when i updated from version 2.3.2.5 to 4.0.1, I got problem with my (unchanged) Javascript client. Data was received as a binary blob instead of a string.
The method that I used in WatsonWsServer.cs, on .NET 6.0.11, was:
public Task<bool> SendAsync(Guid guid, string data, CancellationToken token = default)
My workaround to get it to work as before was to instead call one of the overloads:
I saw in the history that WebSocketMessageType.Text was used in the old
public Task<bool> SendAsync(string ipPort, string data, CancellationToken token = default)
so I guess the type was lost by mistake.
Thanks!
Hello, and thank you for providing WatsonWebsocket. It's a delight to use it :-) But when i updated from version 2.3.2.5 to 4.0.1, I got problem with my (unchanged) Javascript client. Data was received as a binary blob instead of a string.
The method that I used in WatsonWsServer.cs, on .NET 6.0.11, was:
public Task<bool> SendAsync(Guid guid, string data, CancellationToken token = default)
My workaround to get it to work as before was to instead call one of the overloads:
I saw in the history that WebSocketMessageType.Text was used in the old
public Task<bool> SendAsync(string ipPort, string data, CancellationToken token = default)
so I guess the type was lost by mistake. Thanks!