-
Key: DDS-170
-
Legacy Issue Number: 7134
-
Status: closed
-
Source: THALES ( Virginie Watine)
-
Summary:
The "which_added" operations on the collections were designed in the PIM so
that it is possible not to compute any result when the content of the
collection had been totally changed. This is not present in the IDL. *** Proposal [THALES]
change the operation to get a boolean result (true => the information is
returned in the out parameter; false => no information) instead of sending
the information as the result.-
-
- Concrete changes
IDL
abstract valuetype ListBase : CollectionBase {
boolean which_added (out LongSeq indexes);
[instead of LongSeq which_added ();]
...
abstract valuetype StrMapBase : CollectionBase {
boolean which_added (out StringSeq keys);
[instead of StrinSeq which_added ();]
...
abstract valuetype IntMapBase : CollectionBase {
boolean which_added (out LongSeq keys);
[instead of LongSeq which_added ();]
- Concrete changes
-
-
-
Reported: DDS 1.0b1 — Tue, 9 Mar 2004 05:00 GMT
-
Disposition: Resolved — DDS 1.0
-
Disposition Summary:
see below
-
Updated: Fri, 6 Mar 2015 21:40 GMT
DDS — ref-1054: Bad which_added operations in IDL
- Key: DDS-170
- OMG Task Force: Data Distribution Service FTF