Problem/Motivation
Imagine a mechanism to warn for concurrent edits, that on edit pages has some js that pings the server to signal "still editing", and gets back if another client set such a "soft-lock". This would benefit from a improved history repository to store the soft-locks.
Proposed resolution
Add "operation" and serialized "payload/data" to history repotitory.
Remaining tasks
- Decide if this better goes into history repository or be a separate thing
- do it