<< Click to Display Table of Contents >> Navigation:  Technical Documentation > OpenAir SDK > Connection and exchanges with the server > Choosing an AirDDO

At the call of getDDOConfiguration(ddo_id), we keep the ddo_id and we empty the interface.

 

Here is a simplified explanation of the loadDDO behavior:

•Subscription request to AirDDO (call to subscribe(ddo_id))

oIf successful

▪Request channel types (call to getDDOConfiguration(ddo_id), which will fill the interface by instantiating the different tracks if successful)

▪Request content for each track (call to getUpdateChannel(ddo_id, channel), which will fill each track if successful)

 

In parallel, each instantiated component subscribes to app.component or ADMS events to update in real time.3