Interface INopeConnectivityManager

A connectivityManager observes the connection to various dispatchers. This element displays all found dispatchers in the network (if there are no others only itself) in the dispatchers property. It manages the status (dead, slow, warn, alive) of the other dispatchers.

The manager uses a bridge ICommunicationBridge to search for new dispatchers. When a link layer connection is established via the bridge, a so-called bonjour message is sent. With this message all dispatchers in a network register themselves. If such a message is sent, all other dispatchers report their current status. Thus all dispatchers are known to each other.

The connectivityManager checks their status time-based. To do this, all ConnectivityManagerssend each other alivemessage (aheartbeat`) defined time interval. This can be used to monitor when a dispatcher last checked in. If this exceeds a certain time interval, that dispatcher is first classified as 'slow' and then as 'dead'. If the dispatcher does not check in after a defined time interval, it is removed.

The described changes can be observed using the dispatchers property.

In addition, the connectivityManager allows synchronization of timestamps with other systems (usually other dispatchers). This is useful when different systems store sensor data, for example. The timestamp is calculated with a delay, which can be determined during pings.

• You can get a sync timestamp using the now property.

The connectivityManager provides properties that simplify the collection of some information:

• getStatus to get the status of a particular dispatcher.
• getAllHosts: to get all hosts on the network. (It is possible that several nope runtimes are running on the same host)
• upTime: since when the Connectivity Manager is running.

Sometimes it is useful to define a master in the network with nope runtime, (e.g. time synchronization). For this the flag master can be set to true or false. This sets the master mode of the connectivityManager manually. If it is set to null, the master is determined automatically and the connectivityManager could be a master. The selection of the master is based on the operation time and the connection time.

For better understanding please read the 13-ConnectivityManager Jupyter notebook in the wiki-section! *