> - NodeReferences collection handling (JCR-74):
> Sorry for creating the issue :(, now I think it can be closed. Since
> references are stored as PropertyStates, NodeReferences store actions
> are redundant. An add/remove/modify aware object is unnecesary because
> there's already one for PropertyStates.
yes. as far as i remember, the NodeReferences was only introduced to
speedup non-reference-aware persistence backends, such as xml/obj on
fs, etc. in order to build a NodeReferences object, you must gather
all property states that contain a reference value to the respective
target. when using rdbms or similar, this can easily be done in a
simple query, where as in a filesystem, one would have to traverse all
property states.

> - NodeState. Parents and Child Node entries collection handling
> A single add/remove/modify aware object for child node entries would be
> very useful. If a NodeState is added or removed both parent and child
> are stored, a ChildNodeEntryChangeLog would be enough to notify the
> PersistenceManager about changes in parents and children.
true. but i guess, the entire child-node-entries list must be stored,
because the number of added/removed entries could be greater than 1
and for orderable childnode entries, also the ordering of the list
could have been changed.

> - PropertyState. InternalValues collection handling
> An add/remove/modify aware object would be an improvement. This would
> reduce the overhead of writing all the values for multivalue properties.
> This is particularly important in networked deployments. I think that an
> InternalValueId would be needed and it should have the following fields:
> uuid, name, index and type.
true. but we would like to discourage people to make intensive use of
MV-properties. especially the use of binary-mv-properties need a good
legitimacy :-)

-- 
------------------------------------------< [EMAIL PROTECTED] >---
Tobias Strasser, Day Management AG, Barfuesserplatz 6, CH - 4001 Basel
T +41 61 226 98 98, F +41 61 226 98 97 
-----------------------------------------------< http://www.day.com >---

Reply via email to