-
Key: DDS-37
-
Legacy Issue Number: 6743
-
Status: closed
-
Source: Boeing ( Matthew Liu)
-
Summary:
Issue# 2140 Make_USER_DATA_an_array_and_mutable Issue [Boeing SOSCOE] ? There are several potentially independent uses for USER_DATA. It would be useful to have it as a set of name-value pairs or other extensible construct. That way layers such as SOSCOE could add its own USER_DATA and not conflict with the uses that the application above SOSCOE may make of the data. ? SOSCOE has created a provider property class that allows applications to have attributes with typed values; it becomes a triplet (name, type, value). Currently the “type” only supports simple types, but the intent is to extend it to well-known structured types (ref Issue#2035). The extension of the USER_DATA can be used to implement these properties. Proposal [Boeing SOSCOE] ? Make USER_DATA a set of name-value pairs and make it mutable. ? Alternatively keep the USER_DATA as it is for the simple cases and add something more flexible for the more complex cases.
-
Reported: DDS 1.0b1 — Thu, 18 Dec 2003 05:00 GMT
-
Disposition: Resolved — DDS 1.0
-
Disposition Summary:
closed no change
-
Updated: Fri, 6 Mar 2015 20:58 GMT
DDS — Make_USER_DATA_an_array_and_mutable Issue
- Key: DDS-37
- OMG Task Force: Data Distribution Service FTF