...
RDK Shell + Rialto Architecture (Proposed)
Image Removed
Image Removed
Image Added
App'n Launch Life cycle
| draw.io Diagram |
|---|
| border | true |
|---|
| diagramName | test |
|---|
| simpleViewer | false |
|---|
| width | 600 |
|---|
| links | auto |
|---|
| tbstyle | top |
|---|
| lbox | true |
|---|
| diagramWidth | 911 |
|---|
| revision | 16 | 19 |
|---|
|
- initiateApplication - creates a new RialtoSessionServer/RialtoServer instance.
- changeSessionServerState - requests Rialtosessionserver/RailtoServer to change its state
- socketpair is used to create the point-to-point IPC channel used for all Rialto Server Manager to Rialto Application Session Server communications
- Application Session Server sends first message so Server Manager knows that it is now up and running
- Session server creates the socket that the app will use for sending AV data and control respectively.
App'n Suspend Life cycle
| draw.io Diagram |
|---|
| border | true |
|---|
| diagramName | suspend |
|---|
| simpleViewer | false |
|---|
| width | 600 |
|---|
| links | auto |
|---|
| tbstyle | top |
|---|
| lbox | true |
|---|
| diagramWidth | 941 |
|---|
| revision | 11 |
|---|
|
...
- Initial approach was to run RialtoServer RialtoServerManager using systemd during the boot up sequence.
...
After further review it was decided RialtoServer RialtoServerManager shouldn't be started by service file directly.
libRialtoServerManager.so should be responsible for creating an instance of RialtoServer RialtoServerManager which should spawn the socket for running rialto.
...