The program will be blocked when we use the properties of isAlive Act… #644
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…iveID and InactiveID and all methods relatived to ping undering the case of connectivity of any remote client was terminated suddenly.
That's a big problem when we use the software in real time data transferring and the network was interrupted unexpectedly, so I
change them to asynchronous method with setting macro definition of __PING_ASYNC at property of project
1.Steps to reproduce:
Start WebSocketServer
Start two or more clients to connect to WebSocket Server
Unplugged the net cable of one of clients' manually
The property of isAlive ActiveID or InActiveID was used before sending message in WebSocketBehavior or the event of _sweepTimer was triggered at occasion of sending message.
2.Actual result:
All other rest clients could not receiving any data from WebSocket Server in 10 to 30 seconds until the WebSocket Server receiving the event of that client was closed or offline.
3.Expected result:
Send messages quickly and continusly
4.Proposed solution:
Replacing the usage of the ping method with pingAsync