You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 16, 2023. It is now read-only.
It is possible for an endpoint to connect and then disappear. However the communication layer does not verify the status of the endpoint before using it / presenting it to the user, thus making the user believe that the endpoint is active.
There should probably be a protocol level 'ping' message that verifies if an endpoint is still active or not.
The text was updated successfully, but these errors were encountered:
Won't fix this directly. Will provide a way to execute a protocol / interaction level 'ping' upon request, but there is no point in doing a 'ping' before each message because that will increase the data on the line a lot.
It is possible for an endpoint to connect and then disappear. However the communication layer does not verify the status of the endpoint before using it / presenting it to the user, thus making the user believe that the endpoint is active.
There should probably be a protocol level 'ping' message that verifies if an endpoint is still active or not.
The text was updated successfully, but these errors were encountered: