Skip to content

A new model for content update dependencies and constraints

With explicit sync, fifo, commit-timing and transactions we started to have huge problems describing interactions with sync subsurfaces and the "queue" for content updates. We need a model that can describe all of that, preferably as simple as possible, so we can talk about them and use them in the protocol specs.

  1. We need a wayland "docbook" chapter about content updates and their dependencies and constraints (based on !379 (comment 2379250)). This should make clear if the model is usable.
  2. To model should cover explicit sync, fifo, commit-timing and transactions, as well.
  3. When the model proved useful, start moving the protocols over to it.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information