Issue 10728:  set_auto_deref, deref_all, underef_all operations (data-distribution-rtf)
Source: PrismTech (Mr. Erik Hendriks, erik.hendriks(at)prismtech.com)
Nature: Revision
Severity: 
Summary: Problem:
The descriptions of the deref_all, underef_all and set_auto_deref should be stated to be implementation dependant, as these operations basically are only a standardized set of operations which can be used by DLRL applications to optimize the memory usage of the underlying DLRL implementation, but the exact affects and such are impossible to describe on specification level. And whether it is more efficient for an implementation to always load the states or do it on request basis is an implementation issue, so we would like to state for the mentioned three operation that the affects are implementation dependant.
 

Resolution: 
Revised Text: 
Actions taken:
February 13, 2007: received issue
Discussion: 
The affects of the set_auto_deref, deref_all, underef_all operations on the object home should be made implementation dependant.
End of Annotations:=====
s is issue # 10728	From: "Erik Hendriks" <Erik.Hendriks@prismtech.com> 

 set_auto_deref, deref_all, underef_all operations
The affects of the set_auto_deref, deref_all, underef_all operations on the object home should be made implementation dependant.

Problem:
The descriptions of the deref_all, underef_all and set_auto_deref should be stated to be implementation dependant, as these operations basically are only a standardized set of operations which can be used by DLRL applications to optimize the memory usage of the underlying DLRL implementation, but the exact affects and such are impossible to describe on specification level. And whether it is more efficient for an implementation to always load the states or do it on request basis is an implementation issue, so we would like to state for the mentioned three operation that the affects are implementation dependant.