...

Below is the High-Level architecture defined for Ripple used by the Video Accelerator device.

Manifests

Ripple bootstraps three configuration json files during startup these files are referred to as manifests.

There are three types of manifests in Ripple

Device manifest

This manifest contains the below configurations

1. Websocket configuration for internal and 3rd party app secure connections
2. Device platform information
3. Distributor platform information
4. Distributor cloud services configurations
5. Privacy and data governance settings
6. Default values for settings and other known configurations
7. Permission Exclusory
8. Supported Capabilties
9. User grant policies
10. App lifecycle properties
11. Application properties

Sample Firebolt-device-manifest can be found here

App Library

List of applications that are launchable by Ripple. This app library can be empty if the launcher app wants to handle the catalog expectation for this implementation is to use Lifecyclemanagement API(s) provided by the Ripple RPC api(s) defined here.

Sample App library can be found here

Extension Manifest

Extension Manifest defines the list of Extensions needed to be loaded by Ripple to fulfill its contracts. A given Extension manifest contains

1. The default path for all extensions
2. Default extension type for the given platform (.so/.dll/.dylib)
3. An array of extensions each having an id, uses, fulfills, and config fields
4. Required contracts expected by the platform
5. RPC aliases for legacy and other extension support.

Sample Extension manifest can be found here

Ripple SDK

Ripple Main

IEC

Extensions

Bootstrap

Firebolt App Lifecycle 1.0

A Firebolt application needs to comply with the Application Lifecycle policies defined by the schema. 

ADRs

Links and Stuff

TBA