Creates an instance of Bridge.
Bridge
Optional id: string = ...The ID. (this can be adapted later and is only used to simplify debugging)
Flag, indication, whether the Layer is connected or not.
ID of the Layer.
M.Karkowski
ICommunicationInterface
Used to show, whether the the layer receives its own messages
ICommunicationInterface
Function, to add an Layer to the Bridge
ICommunicationBridge
The Layer to Add.
Flag, that enables considering this flag in the connected flag.
used to emit some data on the bride. It will distribute the event accors
M.Karkowski
ICommunicationInterface
used to emit some data.
M.Karkowski
ICommunicationInterface
The Event name
The Callback to use.
Function, to remove the Layer again. Data wont be forwarded any more.
ICommunicationBridge
The Layer to Remove
Readable status of the Connection.
The Statsus
ICommunicationBridge
Generated using TypeDoc
A
ICommunicationBridgeis used to establish different connections (a bridge can establish several connections with different layers).The
ICommunicationBridgeis the core interface with which all Nope core elements interact. Its main task is to add and remove multiple layers (like 'mqtt' or 'io-sockets'; see ICommunicationInterface)To the outside, the bridge behaves like a ICommunicationInterface. I.e. the methods on and emit are also implemented. However, the bridge ensures that each of the ICommunicationInterface added, are able to receive and send the messages. Furthermore the status connected indicates whether all layers are connected or not.
If different layers are only optional, e.g. all connections are covered by io-sockets, but all messages are to be mirrored to MQTT because they are to be picked up there, then this can be taken into account in the add method. These connections are then not taken into account in the connected status.
Export
ICommunicationBridge