Issue 10738: objects instances in a writeable CacheAccess (data-distribution-rtf)
Source: PrismTech (Mr. Erik Hendriks, erik.hendriks(at)prismtech.com)
Nature: Revision
Severity: 
Summary: Problem:

When should objects instances in a writeable CacheAccess be regsitered to the DataWriter? Upon entrance into the writeable CacheAccess or only when actually performing the write operation. This choice may impact ownership matters. Same question for newly created objects in a CacheAccess: when should they be registered?

Solution:

Our proposal is to only register any changes during the write operations, otherwise overhead is very heavy when cloning a large tree of Objects into a writeable CacheAccess. Probably most of these objects will not become modified and then doing a register upon entrance of each instance might result in huge numbers of unnecessary register messages.

TBD.


Resolution: 
Revised Text: 
Actions taken:
February 14, 2007: received issue
Discussion: 
It should be clear when objects instances in a writeable CacheAccess are registered to the DataWriter.
End of Annotations:=====
s is issue # 10738	From: "Erik Hendriks" <Erik.Hendriks@prismtech.com>


objects instances in a writeable CacheAccess 
It should be clear when objects instances in a writeable CacheAccess are registered to the DataWriter.

Problem:

When should objects instances in a writeable CacheAccess be regsitered to the DataWriter? Upon entrance into the writeable CacheAccess or only when actually performing the write operation. This choice may impact ownership matters. Same question for newly created objects in a CacheAccess: when should they be registered?

Solution:

Our proposal is to only register any changes during the write operations, otherwise overhead is very heavy when cloning a large tree of Objects into a writeable CacheAccess. Probably most of these objects will not become modified and then doing a register upon entrance of each instance might result in huge numbers of unnecessary register messages.

TBD