Unification the associated output transports to the input one AND the generic output transport connection

31.03.2023 10:00 Age: 2 yrs Category: By: Roman Savochenko

---

The associated output transports to the input one is about accepting connections at initiative of the external hosts and the localhost is already requesting for these ready connections. That is allowing for holding one server with real-static IP and many external clients with dynamic and "grey" IP. What implemented currently only for Transport.Sockets.

The generic output transport connection is appending the previous mechanism by a convenient way of connection to an external host with automatic transports creation at the normal connections and selection need transport from the external host initiative at its connection identifier.

Processing the initiative connections of the external host is not an ordinal task and early that was meant of creation a custom procedure of registration such connections and their assigning to the corresponded data sources like to ModBus, with the following tracing the connection loss and replacement. And without such task the output transports can flood up to the connections limit.

Currently the mechanism was unified for processing the connections autonomously and at the connection identifier, that is replacing to reconnections with equal identifier. The connection management task-procedure initConAssociateTrs adapted to use the functions conPrm("initConID"), associateTrsList() of the new mechanism and left for the data source objects without support for the generic output transport connection at this time.

Mechanism of the generic output transport connection is used currently in the OpenSCADA external hosts, that is you can already control for the external hosts connected at own initiative to a server, also as access their data through DAQ.DAQGate. This mechanism also used in the module DAQ.ModBus.

For more details see the corresponding part of the 0.9.6 LTS release report.

---