On 27/03/2015 11:48, Dr. David Alan Gilbert wrote: > > So, I like the idea of one message per action in principle - but only > > if that action really is well-defined without reference to what > > operations come before and after it. If there are hidden dependencies > > about what actions have to come in what order, I'd rather bake that > > into the command structure. > > In no way is it hidden; the commands match the state transitions.
So is there only one writer thread? In which states can the other threads read the postcopy state, and why is sequential consistency important? That is, in threads other than the writer, how does reading the state interact with other reads and writes? Paolo
