Issue 10688: Clarify typical scenario for write mode of CacheAccess in section 3.1.6.5.2 (data-distribution-rtf)
Source: PrismTech (Mr. Erik Hendriks, erik.hendriks(at)prismtech.com)
Nature: Clarification
Severity: 
Summary: Problem:
Section 3.1.6.5.2 still talks about the clone_object operation, neglects to talk about the create_unregistered_object/register_objects operations and in step 5 it talks about modifying the attached. (attached what?!) it probably should say objects. Also between step 6 and 7 it should say

Solution:
Replace:
3.1.6.5.2 Write Mode
The typical scenario for write mode is as follows:
1. Create the CacheAccess for write purpose (Cache::create_access).
2. Clone some objects in it (ObjectRoot::clone or clone_object).
3. Refresh them (CacheAccess::refresh).
4. If needed create new ones for that CacheAccess (ObjectHome:: create_object).
5. Modify the attached (plain access to the objects).
6. Write the modifications into the underlying infrastructure (CacheAccess::write).
7. Purge the cache (CacheAccess::purge); step 2 can be started again.
8. Eventually, delete the CacheAccess (Cache::delete_access).
With:
3.1.6.5.2 Write Mode
The typical scenario for write mode is as follows:
1. Create the CacheAccess for write purpose (Cache::create_access).
2. Attach some cloning contracts to it (CacheAccess::create_contract)
3. Execute these contracts (CacheAccess::refresh).
4. If needed create new objects for that CacheAccess (ObjectHome:: create_object or ObjectHome::create_unregistered_object followed by ObjectHome::register_object).
5. Modify the objects (plain access to the objects).
6. Write the modifications into the underlying infrastructure (CacheAccess::write).
7. If needed create new contracts, delete/change exisiting contracts and then goto step 3 again.
8. Purge the cache (CacheAccess::purge); step 2 can be started again.
9. Eventually, delete the CacheAccess (Cache::delete_access).

Resolution: 
Revised Text: 
Actions taken:
February 12, 2007: received issue
Discussion: 
Clarify the typical scenario for write mode of a CacheAccess in section 3.1.6.5.2 and fix typos.
End of Annotations:=====
s is issue # 10688	From: "Erik Hendriks" <Erik.Hendriks@prismtech.com>


Clarify typical scenario for write mode of CacheAccess in section 3.1.6.5.2
Clarify the typical scenario for write mode of a CacheAccess in section 3.1.6.5.2 and fix typos.

Problem:
Section 3.1.6.5.2 still talks about the clone_object operation, neglects to talk about the create_unregistered_object/register_objects operations and in step 5 it talks about modifying the attached. (attached what?!) it probably should say objects. Also between step 6 and 7 it should say

Solution:
Replace:
3.1.6.5.2 Write Mode
The typical scenario for write mode is as follows:
1. Create the CacheAccess for write purpose (Cache::create_access).
2. Clone some objects in it (ObjectRoot::clone or clone_object).
3. Refresh them (CacheAccess::refresh).
4. If needed create new ones for that CacheAccess (ObjectHome:: create_object).
5. Modify the attached (plain access to the objects).
6. Write the modifications into the underlying infrastructure (CacheAccess::write).
7. Purge the cache (CacheAccess::purge); step 2 can be started again.
8. Eventually, delete the CacheAccess (Cache::delete_access).
With:
3.1.6.5.2 Write Mode
The typical scenario for write mode is as follows:
1. Create the CacheAccess for write purpose (Cache::create_access).
2. Attach some cloning contracts to it (CacheAccess::create_contract)
3. Execute these contracts (CacheAccess::refresh).
4. If needed create new objects for that CacheAccess (ObjectHome:: create_object or ObjectHome::create_unregistered_object followed by ObjectHome::register_object).
5. Modify the objects (plain access to the objects).
6. Write the modifications into the underlying infrastructure (CacheAccess::write).
7. If needed create new contracts, delete/change exisiting contracts and then goto step 3 again.
8. Purge the cache (CacheAccess::purge); step 2 can be started again.
9. Eventually, delete the CacheAccess (Cache::delete_access).