On 03/02/16 15:45, A. Soroka wrote:
Okay, as I wrote, I have no objection to pulling out journaling for
now. We can reintroduce it later if that seems useful. Alternatively,
if you would rather fix it up to work with what you are doing, I can
pivot to do that, but it will be a day or two at least. Sounds like
the right move now is to excise it.
"Indeed DatasetGraphWithLock is really some sort of "storage DSG"
(the current DSG interface before adding Transactional) and a
transactional policy (which should be a parameter, not built in).”
You mean some way of building a DSGWithLock using a wrapped dataset
and a lock? Or using a wrapped dataset and some as-yet un-introduced
type that represents policy abstractly?
Roughly that -the policy is a Transactional so the policy is injected.
Boundary markers in streams of changes would indeed be great. I can
think of at least one use case myself, from my $job— just plain
logging changes into a human-intelligible journal.
That is a good example.
--- A. Soroka The University of Virginia Library
