If the client software will be required to monitor a large number of control alias values, the Change Group commands can be used to maximize efficiency. By issuing a single command, you can detect whether any individual controls in a group of controls have changed.
When a control alias is added to the change group, it is considered initially changed, and you can retrieve its value by issuing a get command. You can define multiple change groups using RATC2.
At the initial connect, and after each subsequent deploy or emulate, there will be no change groups, because they are cleared between deployments. If there are no change groups assigned when a Change Group Get command is received, a default change group will be created (but containing no controls), so the response would show zero changes. It is not necessary for the client software to clear the change group before disconnecting – this is done automatically by the MediaMatrix node.
See also |