The MessageBus component implements the message bus that ensures receipt, distribution and delivery of messages between programs running KasperskyOS. This bus is based on the publisher-subscriber model. Use of a message bus lets you avoid having to create a large number of IPC channels to connect each subscriber program to each publisher program.
Messages transmitted through the MessageBus cannot contain data. These messages can be used only to notify subscribers about events.
The MessageBus component provides an additional level of abstraction over KasperskyOS IPC that helps simplify the development and expansion of your programs. MessageBus is a separate program that is accessed through IPC. However, developers are provided with a MessageBus access library that lets you avoid direct use of IPC calls.
The API of the access library provides the following interfaces:
IProviderFactoryProvides factory methods for obtaining access to instances of all other interfaces.
IProviderControlInterface for registering and deregistering a publisher and subscriber in the bus.
IProvider (MessageBus component)Interface for transferring a message to the bus.
ISubscriberCallback interface for sending a message to a subscriber.
IWaiterInterface for waiting for a callback when the corresponding message appears.
Message structure
Each message contains two parameters:
topicIdentifier of the message subject.
idAdditional parameter that identifies a particular message.
The topic and id parameters are unique for each message. The interpretation of topic+id is determined by the contract between the publisher and subscriber. For example, if there are changes to the configuration data used by the publisher and subscriber, the publisher forwards a message regarding the modified data and the id of the specific entry containing the new data. The subscriber uses mechanisms outside of the MessageBus to receive the new data based on the id key.