You are viewing a plain text version of this content. The canonical link for it is here.
Posted to slide-dev@jakarta.apache.org by st...@apache.org on 2004/06/22 20:04:00 UTC

cvs commit: jakarta-slide/proposals/jcrri ToDo.txt

stefan      2004/06/22 11:04:00

  Modified:    proposals/jcrri ToDo.txt
  Log:
  jcrri
  
  Revision  Changes    Path
  1.2       +4 -7      jakarta-slide/proposals/jcrri/ToDo.txt
  
  Index: ToDo.txt
  ===================================================================
  RCS file: /home/cvs/jakarta-slide/proposals/jcrri/ToDo.txt,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- ToDo.txt	28 May 2004 18:23:44 -0000	1.1
  +++ ToDo.txt	22 Jun 2004 18:04:00 -0000	1.2
  @@ -14,21 +14,18 @@
   - provide clean abstraction for persistence grouping (nodes & properties 
     that should be stored/loaded together in the persistence layer);
     (e.g. properties are stored within .node.xml)
  -- state of removed items is currently not deleted in persistence layer:
  -  nodes in transient attic are orphaned, i.e. they are disconnected from 
  -  the hierarchy and can thus not be found anymore on Node#save()
  +- need a more efficient way to persistently remove state of items in transient attic 
  +  (nodes in transient attic are orphaned, i.e. they are disconnected from 
  +  the hierarchy and can thus not be easily identified on Node#save):
     => need a hierarchical cache index for items in the transient attic 
       (see TransientItemStateManager), sparse tree index?; this index needs 
       to be maintained/updated on every transient & persistent hierarchy 
       operation (move, remove, copy)
  -  => alternative approach: flag removed child items in parent's child 
  -    entry list as 'removed'
   - HierarchyManager: cache Path objects (key: ItemId, value: Path[]);
     update cache on hierarchy changes (move, hardlink, remove, etc) 
  -- persist global namespace registry (Workspace#getNamespaceRegistry)
   - inline @todo comments: resolve/implement
   - implement semantics of REFERENCE property type (i.e. referential integrity)
  -- implement 'orderableChildNodes' note type flag
  +- implement 'orderableChildNodes' node type flag
   - multiple parents & NodeDef of child node:
     - the child node adopts the NodeDef at creation time
     - when the child node is removed from this 'first' parent, it should
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-dev-help@jakarta.apache.org