-
Key: TEX11-33
-
Status: closed
-
Source: BAE SYSTEMS ( Mr. Simon Mettrick)
-
Summary:
Section 12.2 (DDS PSM) states that partitions are used to identity (s/b identify) different TACSIT and client instances. An alternative, valid model is to have different separate topic instances for different TACSIT and client instances.
In particular, the DDS security model doesn't work well using partitions. It is better to have separate topic instances then each instance can have its own permissions. -
Reported: TEX 1.0 — Wed, 26 Jul 2023 14:23 GMT
-
Disposition: Resolved — $issue.fixedSpecification.name
-
Disposition Summary:
Allow separate topic instances for different TACSIT instances
This issue is also relevant to the Data Interface DDS PSM, which contains the same statement.
In the DDS PSM, there are no client specific topic instances, therefore reference to clients here is superfluous.
Different TACSIT instances are in effect different picture views. Each TACSIT instance should have its own set of topic instances, made unique (within the system scope) with an appropriate suffix.
-
Updated: Tue, 9 Jan 2024 19:40 GMT
TEX11 — Don't use partitions for different clients
- Key: TEX11-33
- OMG Task Force: TACSIT Data Exchange (TEX) 1.1 RTF