Hi
- 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.
- 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.
Hi Edgar,
as you may have noticed, the ItemStates used by the SharedItemStateManager - either new ones or deserialized from persistent storage - are created by the PersistenceManager implementation itself. Since PropertyState and NodeState are public, non-final classes you may go ahead and derive persistence manager specific subclasses that store additional information useful to your implementation.
Kind Regards Dominique
