Issue 10718: Add attribute to CacheAccess (section 3.1.6.3.3) (data-distribution-rtf) Source: PrismTech (Mr. Erik Hendriks, erik.hendriks(at)prismtech.com) Nature: Revision Severity: Summary: Problem: Currently it is only possible to retrieve the names identifying the object homes for which a CacheAccess contains objects, but it would be desirable if instead of getting an array of string you'd get an array of indexes. This would allow for a more performance friendly way for applications to jump to the code to handle objects of a specific type in a CacheAccess Solution: Add the following row to the attributes listing of the CacheAccess directly following the row for attribute type_names: contained_types integer[] Add the following description to the list of description for attributes on page 3-21 directly following the description of attribute type_names: o A list of indexes that represents the types for which the CacheAccess contains at least one object (contained_types). In the IDL description on page 3-57 section 3.2.1.2 add attribute definition in the interface CacheAccess: readonly attribute LongSeq contained_types; In figure 3-4 on page 3-16 add the contained_types to the attribute listing of class ObjectHome. Resolution: Revised Text: Actions taken: February 13, 2007: received issue Discussion: Add attribute to CacheAccess (section 3.1.6.3.3) to get the contained_types based upon the home indexes instead of the homes names. End of Annotations:===== iler: QUALCOMM Windows Eudora Version 7.0.1.0 Date: Tue, 13 Feb 2007 16:29:08 -0500 To: issues@omg.org, data-distribution-rtf@omg.org From: Juergen Boldt Subject: issue 10718 -- DDS RTF issue X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at omg.org This is issue # 10718 From: "Erik Hendriks" Add attribute to CacheAccess (section 3.1.6.3.3) Add attribute to CacheAccess (section 3.1.6.3.3) to get the contained_types based upon the home indexes instead of the homes names. Problem: Currently it is only possible to retrieve the names identifying the object homes for which a CacheAccess contains objects, but it would be desirable if instead of getting an array of string you'd get an array of indexes. This would allow for a more performance friendly way for applications to jump to the code to handle objects of a specific type in a CacheAccess Solution: Add the following row to the attributes listing of the CacheAccess directly following the row for attribute type_names: contained_types integer[] Add the following description to the list of description for attributes on page 3-21 directly following the description of attribute type_names: o A list of indexes that represents the types for which the CacheAccess contains at least one object (contained_types). In the IDL description on page 3-57 section 3.2.1.2 add attribute definition in the interface CacheAccess: readonly attribute LongSeq contained_types; In figure 3-4 on page 3-16 add the contained_types to the attribute listing of class ObjectHome. Juergen Boldt Director, Member Services Object Management Group 140 Kendrick St Building A Suite 300 Needham, MA 02494 USA tel: +1 781 444 0404 x 132 fax: +1 781 444 0320 email: juergen@omg.org www.omg.org