casparcg-connection icon indicating copy to clipboard operation
casparcg-connection copied to clipboard

Command timeout/reconnection strategy

Open jesperstarkar opened this issue 7 years ago • 2 comments

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:

  1. Discard
  2. Retry (max attempts)
  3. Verify and choose (test a simple INFO-command, then choose to discard or retry)

jesperstarkar avatar Jul 19 '17 13:07 jesperstarkar

PING command added in 2.1.x onwards ... but still an issue for 2.0.7.

sparkpunkd avatar Jul 18 '19 15:07 sparkpunkd

Discard has issues - we end up sending multiple commands again.

jesperstarkar avatar Jun 07 '22 09:06 jesperstarkar