Versions Compared

Old Version 4

changes.mady.by.user Pradeepta Kumar Das

Saved on

compared with

New Version 5

changes.mady.by.user Lakshmipriya P

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Two applications connected to a same instance of IARM-Bus are able to exchange events or RPC calls. On a typical system, only one instance of IARM-Bus instance is needed. If desired, it is possible to have multiple IARM-Bus instances. However, applications connected to different buses will not be able to communicate with each other.


 Image RemovedImage Added

1.1 Bus Daemon

...


 The directory under IARM should use this structure:


Directory

Files

$iarm

IARM Core, IARM Bus Daemon, and all IARM Manager Components

core

Core implementation of IARM framework. It is built into a shared library for all IARM applications to use.

core/include

Public headers exposed by IARM core. IARM application should only reference header files located here to use IARM-Bus APIs.

<mgr>

Manager's internal implementation. Header files listed here should NOT be referenced by any external components outside the <mgr> directory.

<mgr>/include

Public headers exposed by the Manager. IARM applications uses the Manager's events or RPC methods should only reference header files located here.

template

A Sample implementation of a IARM Manager Component. This provides a good starting point for developers to create their manager components. The developer can make a copy of the template and modify to suit their application needs.



The IARM-Bus Library is ./core/libIARMBus.so. All IARM Applications must link to this library. 
In this document we use the implementation of IR Manager as our example. The source code of IR Manager is available at iarm/ir/. 
IR Manager is an application that publishes Remote Key events to other applications.

...