Hi, OAK-2287 made me think if we should generalise the approach implemented in OAK-2287 (which is just for jcr:lastModified) in order to make conflict handling more clever.
For example, consider a property myapp:lastActivated (a time stamp). Should we allow such application logic to specify for the conflict handler that the last write (highest value) always wins? There could be complications like another property myapp:lastActivatedBy (a user name) where also the last value should win for the node to be in a consistent state. So overall, I am really not sure if this is a good idea or if we need it at all. Any thoughts? Michael
