Changes between Version 5 and Version 6 of GROUP_PRO_LIB_PERFORMANCE_R0


Ignore:
Timestamp:
05/07/09 13:31:59 (16 years ago)
Author:
gogov
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GROUP_PRO_LIB_PERFORMANCE_R0

    v5 v6  
    4141 
    4242Solving the notification issues will be accomplished with the introduction of Aspects: 
    43  * an Aspect is a Pro, so listeners can be attached and detached to/from it. 
     43 * an Aspect is a BasePro, so listeners can be attached and detached to/from it. 
    4444 * BaseProList will use Aspects internally to reduce the attached listeners and the registered reads. This way: 
    45   * lots of reads should be registered with the ProList itself but with an Aspect of the ProList, and so lots of listeners will be attached to the Aspects, instead of the ProList 
    46   * ProChanges will be fired from the Aspects of the ProList to registered listeners, instead of always firing from the ProList itself. 
    47  * the internal list which actually holds the elements in a ProList is the CacheList. Its access and mutator methods register reads to the whole ProList. Instead of doing this, these methods will be modified to register reads only to affected aspects of the ProList. 
     45  * lots of reads should be registered not with the BaseProList itself but with an Aspect of the BaseProList, and so lots of listeners will be attached to the Aspects, instead of the BaseProList 
     46  * ProChanges will be fired from the Aspects of the BaseProList to registered listeners, instead of always firing from the BaseProList itself. 
    4847 
    4948At first, there will be two types of Aspects: 
    50  * A '''size''' Aspect which AutoProperties interested in only the size of a ProList will attach listeners to. 
    51  * A set of '''key''' Aspects. When using findOne() and findAll() methods of a ProList, a key is used to find all elements of the ProList which have the given key. So a key Aspect for each set of elements having the same key will be present and when the ProList changes but this set doesn't, an AutoProperty which depends only on this set won't get updated. 
    52  
    53 When firing ProChanges from a given Aspect of the ProList, they will be coupled with a respective ProChange fired from the whole ProList and only these mirroring ProChanges will get registered in the ChangeManager responsible for the ProList. Changes fired from Aspects need not and won't be registered. 
    54    
     49 * A '''size''' Aspect which AutoTrackers interested in only the size of a BaseProList will attach listeners to. 
     50 * A set of '''key''' Aspects. When using findOne() and findAll() methods of a ProList, a key is used to find all elements of the BaseProList which have the given key. So a key Aspect for each set of elements having the same key will be present and listeners will be attached to this Aspect, instead of the BaseProList. When the BaseProList changes but this set doesn't, an AutoTracker which depends only on this set won't get updated. 
    5551 
    5652= Implementation =