Kerry Jiang
Kerry Jiang
If your analysis is true, you probably can fix it by switching to SuperSocket.WebSocket. I believe the latest SuperSocket doesn't have this sending issue.
OK, let me review the code again and then give you an update!
SuperSocket.WebSocket is the preferred one and they are supposed to be same.
It is not supported in SWS 0.8, you can try the latest source code in the repository.
Are you sure the connection experienced the socket error is the one you think can send ping and receive pong?
How do you know? From: Henry Su [mailto:[email protected]] Sent: Thursday, March 3, 2016 11:17 AM To: kerryjiang/SuperWebSocket [email protected] Cc: Kerry Jiang [email protected] Subject: Re: [SuperWebSocket] WebSocketServer的SessionClosed触发后，并没有与客户端进行断开 (#30) socket 是tcp通道会经过三次握手的，应该是同一个 Best...
Probably you can implement this feature using endpoint runtime replacement like the code below: https://raw.githubusercontent.com/kerryjiang/SuperSocket/v1.6/QuickStart/WindowsAzure/SuperSocketRole/WorkerRole.cs
AsyncTcpSession? 这个代码有点老啊
为什么在Task.Run里面？能debug吗？
Debug的时候把Performance Profiler打开。