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
Since there's no ping-protocol in AMCP, only sent messages can probe the socket's state. This can not be done at a lower level, due to node.js net.Socket restrictions.
So, when a command times out, we can expect the Socket to be down, IF the command was sent properly (which we normally can expect).
At the moment, we discard sent commands that time out. This should be one of three options:
Discard
Retry (max attempts)
Verify and choose (test a simple INFO-command, then choose to discard or retry)
The text was updated successfully, but these errors were encountered:
Since there's no ping-protocol in AMCP, only sent messages can probe the socket's state. This can not be done at a lower level, due to node.js net.Socket restrictions.
So, when a command times out, we can expect the Socket to be down, IF the command was sent properly (which we normally can expect).
At the moment, we discard sent commands that time out. This should be one of three options:
The text was updated successfully, but these errors were encountered: