David Baird

Thanks for reporting this. Which side is initiating the close? When initiating close from easywsclient, it will do this: 1. It will queue a opcode=close (0x8) message for transmission in...

Hi @Kertopher, this code hasn't been yet written to work with the Code::Blocks / MinGW compiler; But let me know what steps you do to get it working. And adding...

Hi @gity2020 - thanks for the report. Give me a couple days to look into this. To clarify, is this what you see: 1. You try to open a new...

Thanks for your patience while I looked into this. I am taking a guess that getaddrinfo() probably returns ipv6 and ipv4 address, and that is why you get two iterations...

Hi @gity2020 - I just wanted to check: did the last message help at all with your issue? Let me know so I can close this if your issue has...

Hi @jpek42, sorry for taking awhile to get back to this issue. This is a limitation of the API: The information about text or binary can be inspected based on...

Hi @jpek42, the original issue you raise is accurate: this is a limitation of the API, and also unexpected/confusing. The easiest solution would be: make sure that your service ever...

I'd like to help you get this working, but I'm going to need more information. Can you post a gist with the most minimal example possible that illustrates your issue?

Let's break this into three distinct issues. 1. The way you are accessing wss from multiple threads is not safe. You'll need to guard each access to wss with a...

@vinodg - You could open two (or more) web socket connections, one per thread. Then you can get even better than full duplex :) I am willing to consider API...