In other words, Composer Pro is now version-independent of Drivers and Agents, which in turn makes it version-independent of Director. Now, new features can be added to Composer software while still allowing Composer to communicate to Drivers and Agents through a versioned API.įor systems running Control4 OS 3 or higher, versioned APIs between Composer Pro and Drivers and Agents allow the two components to be version-mismatched. With the release of Composer Pro 3.1, communication between Composer Pro and Drivers and Agents were made part of a versioned API. Here’s a simplified view of the prior relationships among these components: When any API was added, changed, removed, or in some cases just used differently, all other components had to be revised to match. This was necessary because these components communicated with each another through conventional Application Programming Interfaces, or APIs. When a revision to one of these components was published, they were all updated together. Prior to this release, Composer Pro, Control4 OS updates, and Drivers and Agents were all released at the same time. But most importantly, Composer Pro can now be released independently from Control4 OS releases which clears the path to accelerated enhancements, features, and fixes to Composer software.
The change allows Composer Pro to connect to any controller running OS 3 or newer. With the release of Composer Pro 3.1, Composer Pro now connects to Director running on the primary controller through a set of versioned APIs.
0 kommentar(er)
