Denis Zykov

Yes, you need some synchronization before `CreateMessageWritter` because parallel read/write is [not supported](https://github.com/vtortola/WebSocketListener/issues/120). `SemaphoreSlim` is fine, queue and async state machine, TPL Dataflow queue is also solution for this problem....

True, no mention of this behavior in docs. I will fix this.

Hi @ManoLazar! WebSocket instance doesn't have *control flow*, so it can't emit events or even update it's internal state (IsConnected, etc) till `ReadMessageAsync` is called. So it is mandatory to...

Actually I can't reproduce. Writing into disconnected socket leads to: a) error b) success not hung. Also it's reporting disconnect on next `ReadMessageAsync ` by returning `null` message. Can you...

Hi everyone. This one is fixed in [4.2.14](https://www.nuget.org/packages/deniszykov.WebSocketListener/4.2.14) Also don't forget to call `webSocket.CloseAsync()` after you are done with WebSocket and want to dispose it. I see in your example...

Hi @chachew! `webSocket` has `IsConnected ` property. And `null` message is received on remote party disconnect.

Currently my goal to release stable version. Then maybe some features including performance counters.

Hi Peter! Thanks for report, I will check it.

It is ping related. As temporary workaround you could disable pings with `options.PingMode = PingMode.Manual`. I will investigate further.

Without ping feature you wont notice lost client until TCP connection is terminated and error popped. TCP connection timeout varies from 30secs to 2mins,