Websocket - beta vs. gamma

image
sendString (websocket) behaves different to the websocket pack in beta. when i send a string with the beta websocket server, i get the same string in chrome dev console data:{“State”:“text”}

when i try the exact same thing with gamma with sendString, i get something called “blob”, looks like this is some array of bytes or something, just no string. looking inside the node in gamma shows some mutable bytes stuff going into the watson sendAsync. any idea how i can make this more compatible with the webworld, really sending a string instead of bytes ?

image
i was able to convert the blob on javascript side

is the messagetype not implemented right in the wrapper ?

indeed, this was the case. thanks for the pointer.

at the time of implementation, the underlying lib didn’t have support for messagetype “text” yet. meanwhile it’s available and i’ve updated the nuget accordingly. see version 0.2.0-alpha of VL.IO.WebSocket

1 Like

image
thanks, i tried the nuget, it is capable of sending strings but you need to change the patch and choose the right send async with string input, which wasn’t done in the nuget.

indeed my bad, only did it for the client. 0.2.1-alpha also has this fixed for the server.

1 Like

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.