Preparing a migration path to keto, and thinking i...
# talk-keto
b
Preparing a migration path to keto, and thinking in terms of parity. We have a distributed locking system that needs to be accounted for (tldr a lock carries a secret that auths mutations in a way that one user, in one tab, can edit a thing). Has anyone expressed a locking policy through opl? I'm thinking
editors
vs
activeEditor
, where active editor is a one-user subset of editors. With this, our domain logic would control the single active editor. That's my first draft, but I'd be interested if this problem has been solved before.