On an abstract level, an Ember+ provider as specified in the Ember+ Specification^[1] can be seen as a database for elements (an element can either be a parameter, a node, a matrix or a function). When an Ember+ consumer connects to a provider, the consumer queries the provider and builds an (often partial) local copy of the database. The two databases are then kept in sync through the exchange of appropriate messages until the consumer decides to terminate the connection.

The types in this namespace aim to automate the above process such that client code can transparently use the local copy of the database and mostly not care about the following:

• How changes from the provider are applied to the local copy of the database

• How local changes are applied to the provider database

• Whether the consumer is still connected to the provider

Proceed to Page 3: Dynamic Interface.