You will find below our Server / Sink Status screen for our DACS 7.5 :
Our question is why and how some client connections have jDacsLib = dacs6.3.0.F1 and other dacs7.3.0.F1 ?
Where this library is coming from ? We found that on our local TREP infra we have dacs7.5.0.F1 which seems ok with the left column "Sink Daemon".
On our side, there is one thing which is changing between client connection having dacs6.3.0.F1 or dacs7.5.0.F1 is that the first ones are using rfaj7.2.0.E3.jar and the seconds are using rfaj8.2.0.L2.jar. Is it expected ?
jDacslib.jar is included within OpenDACS SDKs, and facilitates connectivity to DACS, the version is that of OpenDACS SDK used for the integration and should manifest via DACS UI, but I believe this is not addressing the core of your question.
jDacslib library (jar) is not made available with Java RFA SDKs and Java RFA API is not open source.
However, jDacsLib.class, as well as other dacs functionality classes, are included within rfa.jar for JRFA 8.2 and JRFA 7.6. DACS functionality that is included within the library release should be DACS functionality available and compatible, at the time of the release of RFA, which would be different for JRFA 8.X and RFA 7.X.
This may be why on connectivity to DACS sink daemon it will manifest as the version of jDAClib class within RFA connection by the consumer, and may address the core of the question?
I checked and found that RFA Java 8.2.0.L2 uses dacs7.3.0.F1 and RFA Java 7.7.1.L4 uses dacs6.6.0.F2. Therefore, the version of DACS used by RFA Java 7.2 will be older than dacs6.6.0.F2. It is expected.