Changes between Version 4 and Version 5 of GROUP_FILE_ACCESSES_PERSISTENCE_R0

Timestamp:

11/06/09 15:38:42 (15 years ago)

Author:

mira

Comment:

--

GROUP_FILE_ACCESSES_PERSISTENCE_R0

@@ -44 +44 @@
 For backward compatibility the KEY_KIND should implement the persistence logic in more specific way: First it should call the StringPersister for the attribute “kind” of the given storage. If the given options point it is a save mode this is all but if you are loading there should be a check if this is an old resource and its kind is just “frame”. In that case you should get the child “content” of the given storage and get its attribute kind. Then you should compose the string to be set to the value ref by the content type + “-frame”. [[BR]] [[BR]]
 There are some other model keys that override the persistR3 method to implement specific logic or for backward compatibility. [[BR]] [[BR]]
-ImmList [[BR]] [[BR]]
-ChannelPersister [[BR]] [[BR]]
-
+Most persisters for immutable will inherit an base abstract class RefToStoragePersister that is constructed from an class and implements the getSchema method using the PersistenceUtil. [[BR]] [[BR]]
+There should be abstract class ImmCollectionPersister<E, L> that should provide common logic for persistence of collections. It should have method getElementsType() that returns the class of the objects kept in this collection. This is going to be used to get the appropriate schema for persistence of the kept objects. This class should also have abstract method persistElements, that takes as arguments: the value ref to the collection, the storage, the persistence options and size of the collection. The persist method just gets the size of the collection and calls the persistElements method with the appropriate arguments. [[BR]] [[BR]]
+There should be abstract class ImmListPersister<E, L extends ImmList<E>> that provides common logic for persistence of lists. It provides two abstract methods for different list persisters to implement - createEmptyList and addToList. It should give the common implementation of the persistElements method using those methods. Then The NaiveImmListPersister and ImmTreeListPersister would just implement the two methods that create an empty list of the required type and add elements to it. [[BR]] [[BR]]
+There will be needed a helper method in the ResourceRefList to persist ref lists is specific tags to be compatible with previously saved books. It will take one extra argument – the tag name for the list elements. Its logic will be similar to the collections persistence. [[BR]] [[BR]]
+For Channels common logic will be needed an abstract ChannelPersister. It should provide method for saving all entries in the map of the channel – persistEntries. It should prvide an abstract method getValueClass that gets the class of the timed values (for ActivationChannelPersister this is the TimePos.class and for LocationChannelPersister it is the ImmPoint.class). This method will be used to get appropriate schema for saving the entries by PersistenceUtil method – getImmEntrySchemma.All ChannePersisters should use it in their persist method. To handle the persistence of the different ImmEntry objects should be created an abstract ImmEntryPersister<K, V> that just needs the two methods: getKeyClass() and getValueClass(). It is good to be made TimelineEntryPersister that simply returns TimePos.class for key class. The other method could be implemented directly on the registration the persister object. [[BR]] [[BR]]
 
 = Implementation =