When a remote client makes a change and commits it, it seems that the
CDOInvalidationNotification which other clients receive contains only the
notifier object, and no information about which feature changed, or the
previous or new values. It's left to me to write diff'ing code to figure
that out ;) Is this going to be fixed in future versions, or has it
already been fixed on trunk? It'd be nice if the type of the notification
was INVALIDATE_ADD, INVALIDATE_ADD_MANY, INVALIDATE_REMOVE,
INVALIDATE_SET, etc., so that client code could decide whether to forward
it as a regular ADD, ADD_MANY, etc. notification, or to do something like
wrap it in a write transaction (if they are using EMF Transactions, which
we are.)