/ doc / tocInheritance / IP / PConcurrent / StreamProcessor / __TOCDet / Attribute / Description

Description

Edit keys at this level only

= Implements the storage mechanism for AgoRapide.0x000D0x000A0x000D0x000ACoordinates the -PropertyStream- with other nodes.0x000D0x000A0x000D0x000ATODO: Implement discarding of data when not listening to incoming connections (saves memory usage).0x000D0x000ATODO: (search for this TODO in code to see where relevant to make changes).0x000D0x000A0x000D0x000AHas the following functionality:0x000D0x000A(note: Terminology is kept close to the one used for the MQTT protcol, although AgoRapide does not use MQTT in itself)0x000D0x000A0x000D0x000A1) Listen to incoming TCP/IP connections from other nodes. An incoming connections may be either for:0x000D0x000A   a) Incoming data (from a publishing client), for us to distribute.0x000D0x000A      (0x000D0x000A         as a -CoreDB- we would then store the data locally and          then distribute the data to all current downstream subscriber clients as relevant according to their respective subscriptions          (Note: For incoming data on an incoming connection an implicit -IsAll-, '+*', is assumed),          as a -ArmDB- we would then forward the data to a -CoreDB-      )0x000D0x000A      or for0x000D0x000A   b) Outgoing data, downstream subscribing client requests subscription0x000D0x000A      (0x000D0x000A        we would then typically be a -CoreDB- or a -ArmDB-.0x000D0x000A        After having reveived the -Subscription- and -ClientUpdatePosition-0x000D0x000A        from the subscribing client we will then keep the client continously up-to-date with new data.0x000D0x000A      ).0x000D0x000A0x000D0x000A2) Connect to other nodes. An outgoing connection may be either for0x000D0x000A   a) Publishing properties.       (         As a publishing -Client- the data would be locally in-application generated properties.0x000D0x000A         As an -ArmDB- the data would typically have been received over an incoming connection from a -Client-      )0x000D0x000A      or for0x000D0x000A   b) Receiving (as downstream subscribing client) data from upstream server.0x000D0x000A      (0x000D0x000A        We would then typically be an -ArmDB- or -Client-0x000D0x000A        We would send -Subscription- and -ClientUpdatePosition- as soon as connection is established.0x000D0x000A      )0x000D0x000A0x000D0x000A

Edit keys at all sub levels.
NOTE: Edits are always additive. Use 'Invalid' in order to delete keys.

Generated 2025-06-20 08:08:23.645 UTC