-
Key: DDS12-48
-
Legacy Issue Number: 9530
-
Status: closed
-
Source: THALES ( Virginie Watine)
-
Summary:
Summary:
The OID currently consists of two numbers: a creator_id and a local_id. The philosophy is that each writer should obtain its own unique creator_id, and can then sequence number each object created with it to obtain unique object identifiers. The specification does not specify how the writers should obtain their unique creator_id. Building a mechanism to distribute unique OIDs requires knowledge about the underlying system characteristics, and this information is only available in DCPS.
Proposed Resolution:
Make the definition of the OID vendor specific. This allows a vendor to specify its own algorithms to guarantee that each object has got a unique identifier.
The only location where the application programmer actually has to know the contents of the OID is in the create_object_with_oid method on the ObjectHome. However, we see no use-case for this method and propose to remove it. -
Reported: DDS 1.1 — Mon, 3 Apr 2006 04:00 GMT
-
Disposition: Resolved — DDS 1.2
-
Disposition Summary:
see above
-
Updated: Fri, 6 Mar 2015 20:58 GMT
DDS12 — Representation of OID should be vendor specific
- Key: DDS12-48
- OMG Task Force: Data Distribution RTF 3