News for hackers. Stuff that matters.
Re:You Cannot Correctly Represent Change Without Immutability by Retric on Wednesday July 04, 2012 @12:38PM (#4199987)
Not really you can keep objects locked independently.

  A->A(30)->A(29)...A(0)
  B->B(20)->B(19)...B(0)
start adding a new A; start adding a new B; Finish adding a new A; Finish adding a new B; Verify B; Verify A;

  A->A(31)->A(30)->A(29)...A(0)
  B->B(21)->B(20)->B(19)...B(0)
Now keep A and B's states stored on different machines and they become completely independent with no concept of time or ticks being introduced.

As to an actual example of this in use think bank accounts in an MMO, you might want a transaction log, but you don't necessarily care about time-stamps all that much.

There are no comments on this comment yet.