Val

Hi! That is very strange. Do you think it would be possible to create a small project reproducing the problem? Cheers.

:+1: It should allow you to open connections as long the machine allow you too. My performance tests tried to demonstrate that the component scales up to the max machine's...

Hi! I did some benchmarking, but in Windows. https://github.com/vtortola/WebSocketListener/wiki/WebSocketListener-performance-tests Anyway, if you find any issue let me know. I would be interested in improve it, and I would be happy...

Yes, you will need to implement your own presence control. If you are planning to run your application in only one server you can have a concurrent collection where you...

Hi! It should https://blogs.msdn.microsoft.com/dotnet/2017/10/10/announcing-uwp-support-for-net-standard-2-0/ Let me know if that is not the case.

Hi, I added a new sample about [using WSL as Windows Service](https://github.com/vtortola/WebSocketListener/tree/master/samples/WebSocketListenerService). Let me know if you have any question. Cheers.

Same thing. On the start method, create a `WebSocketListener` and start it, and in the stop method, dispose it.

Hi!, the component does not serve HTTP content. You may want to take a look to [HttpListener](https://msdn.microsoft.com/en-us/library/system.net.httplistener%28v=vs.110%29.aspx). The only thing is that you will need to run the websocket server...

I think you have seen the part about [custom HTTP negotiation](https://github.com/vtortola/WebSocketListener/wiki/Hooking-into-the-HTTP-negotiation), but it is only to hook some logic in case you want to check for example headers like `Cookie`...

I understand it is something that seems convenient, but definitely this is something I won't add, since it goes beyond the WebSocket spec. Cheers.