If you like BoxMatrix then please contribute Supportdata, Supportdata2, Firmware and/or Hardware (get in touch).
My metamonk@yahoo.com is not reachable by me since september. Please use hippie2000@webnmail.de instead.

AVMIPC-Datastore

From BoxMatrix


BoxMatrix >> System >> AVMIPC-Datastore @ BoxMatrix   -   IRC-Chat   -   Translate: de es fr it nl pl
News Selectors Models Accessories Components Environment Config Commands System Webif Software Develop Lexicon Community Project Gallery

Devices Filesystems Partitions Sockets Pipes Interfaces Bridges Ports Events Sources Sinks AVMIPC Processes Watchdogs Memory Slab Vmalloc ProcFS SysFS Research

Info
The AVMIPC-Datastore is a high level messaging pool maintained by avmipcd. It consists of named nodes which can either be AVMIPC-Events which are a stacked stream of triggers and information or AVMIPC-States which represent a snapshot of information in time. Both behave similar, thats's why this Wiki will use the term AVMIPC-Nodes when talking about both. Nodes can have listeners which can communicate through the node using avmipc capable endpoints, which are a special form of Linux-Sockets. Nodes can have attached data in which case the Size column in the tables below is non zero. Attached data uses the JSON format.

There are 2 special events: Every avmipc listener is automatically subscribed to the @ event, regardless of which event or state it is interested in, that is what aicmd -e lists. Every avmipc_command capable listener is subscribed to the aicmd_listener event, that is what aicmd -l lists. All nodes and attachments of the AVMIPC-Datastore can be listed using the aicmd avmipcd datastore show [full] or aicmd avmipcd datastore query <pattern> [full] commands, which normally just list the nodes. in full mode they also list the JSON attachments. In these listings AVMIPC-Events have a leading @, AVMIPC-States do not.

Unlike the AVM-Events which make it easy to find a sender of an event by its Event-Source there is no way to find out the senders to AVMIPC-Nodes automatically. The datastore only lists listeners, the senders have to be researched manually, which is a very complicated task. In fw 6.88 there was no way to list the datastore, since avmipcd was no aicmd listener yet. That is why all Firmware info here starts with fw 7.01.


AVMIPC-Datastore[edit]

Goto:   AVMIPC-Events   -   AVMIPC-States   -   Libraries

AVMIPC-Events[edit]

Events are triggers or notifications sent to all listeners and mostly do not have attached JSON data.
Unlike AVMIPC-States evets are stacked. No event gets lost, all events reach all listeners.
Possible attachments belong to the respective event and are not replaced by the next event.
Together with their owner events all attachments reach all listeners.
A good example is libpcp_itemstatus, which would not work as a state.

Daily updated index of all avmipc events found scanning Supportdata2 probes. Last update: 2022-06-26 05:19 GMT.
The label (avmipc) in the AVMIPC-Event column shows there are other objects in this wiki using this name.
The Mod column shows the amount of models using the respective event. Click the column header to sort by this number.

AVMIPC-States[edit]

States are status informations sent to all listeners and mostly have attached JSON data.
States are not stacked like events, they represent the current snapshot of information, regardless of what happened before.
Senders do not need to submit the complete attachment, they can create or delete it or just change single values in it.

Daily updated index of all avmipc states found scanning Supportdata2 probes. Last update: 2022-06-26 05:19 GMT.
The label (avmipc) in the AVMIPC-States column shows there are other objects in this wiki using this name.
The Mod column shows the amount of models using the respective state. Click the column header to sort by this number.

Libraries[edit]

AVM uses quite some Shared-Libraries to maintain avmipc events and states, see the Events section each:

TODO[edit]

Check the avmipc events of:

Fact-Box