Issue 10734: Add an operation to the Cache (data-distribution-rtf)
Source: PrismTech (Mr. Erik Hendriks, erik.hendriks(at)prismtech.com)
Nature: Revision
Severity: 
Summary: Problem:

Currently when an application is interested in the creation/modification/deletion of specific objects, he can attach a Listener to the corresponding ObjectHome. We will then get separate callbacks for each object of this type that gets created/deleted/modified. But maybe the user doesn't want all these separate callbacks and just wants to deal with a subset of all possible events (for example only creations). He could do so by not attaching ObjectListeners to the ObjectHomes, but by using the CacheListener and then iterate through all Homes using for example only the get_created_objects. It would be nice if the Cache could then return a list of Homes that contain information that needs to be processed, to prevent the user from also having to iterate through all homes that have nothing to report.

Solution:

Add an operation to the Cache that returns a list of indexes for all homes that received updates in the current update round. 

Section 3.1.6.2, Figure 3-4: Add an operation to the Cache called "get_updated_home_indexes".

Section 3.1.6.3.9: Add the following entry to the table:

Cache
operations
get_updated_home_indexes		integer[]

Section 3.1.6.3.4
Add:

·	retrieve the indexes of all ObjectHomes that received updates in the current update round (get_updated_home_indexes).


Section 3.2.1.2: Add to the IDL of the Cache interface the following line:

LongSeq get_updated_home_indexes( );
 

Resolution: 
Revised Text: 
Actions taken:
February 14, 2007: received issue
Discussion: 
Add an operation to the Cache to retrieve the Homes that have received information that needs to be processed.
End of Annotations:=====
s is issue # 10734	From: "Erik Hendriks" <Erik.Hendriks@prismtech.com>


Add an operation to the Cache
Add an operation to the Cache to retrieve the Homes that have received information that needs to be processed.

Problem:

Currently when an application is interested in the creation/modification/deletion of specific objects, he can attach a Listener to the corresponding ObjectHome. We will then get separate callbacks for each object of this type that gets created/deleted/modified. But maybe the user doesn't want all these separate callbacks and just wants to deal with a subset of all possible events (for example only creations). He could do so by not attaching ObjectListeners to the ObjectHomes, but by using the CacheListener and then iterate through all Homes using for example only the get_created_objects. It would be nice if the Cache could then return a list of Homes that contain information that needs to be processed, to prevent the user from also having to iterate through all homes that have nothing to report.

Solution:

Add an operation to the Cache that returns a list of indexes for all homes that received updates in the current update round. 

Section 3.1.6.2, Figure 3-4: Add an operation to the Cache called "get_updated_home_indexes".

Section 3.1.6.3.9: Add the following entry to the table:

Cache
operations
get_updated_home_indexes		integer[]

Section 3.1.6.3.4
Add:

·	retrieve the indexes of all ObjectHomes that received updates in the current update round (get_updated_home_indexes).


Section 3.2.1.2: Add to the IDL of the Cache interface the following line:

LongSeq get_updated_home_indexes( );