Kerry Jiang

看看CPU和内存内存占用率。

https://github.com/kerryjiang/SuperSocket/blob/2858a320d911ecebe1c5656366c10f0bee7aaa79/samples/AspNetSample/Program.cs#L8-L25

Yes, you can. https://github.com/kerryjiang/SuperSocket/blob/d0e5bcfe363dd0ee3a4bacff3f8bc16a8cf9301e/test/SuperSocket.Tests/MainTest.cs#L541-L580

Try register ISessionContainer to the global DI context.

Try "Enable TLS with a certificate in your local certificate store" https://docs.supersocket.net/v2-0/en-US/Enable-Transport-Layer-Security-TLS-in-SuperSocket

Please refer to https://github.com/kerryjiang/SuperSocket/issues/620

Good catch! I am fixing it.

Made a fix for it: https://github.com/kerryjiang/SuperSocket/commit/e758bd6ef045e77af1ef534382e71bbefcf3fc08

These are samples: https://github.com/kerryjiang/SuperSocket/tree/master/samples/WebSocketServer https://github.com/kerryjiang/SuperSocket/tree/master/samples/WebSocketPushServer https://github.com/kerryjiang/SuperSocket/tree/master/samples/LiveChat

If you don't want to support TLS, just remove the tls listener node. https://github.com/kerryjiang/SuperSocket/blob/master/samples/WebSocketPushServer/appsettings.json In SuperSocket.WebSocket, we don't have a concept of routes. But you can get the path from...