• If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Stop wasting time looking for files and revisions. Connect your Gmail, DriveDropbox, and Slack accounts and in less than 2 minutes, Dokkio will automatically organize all your file attachments. Learn more and claim your free account.


Enitites vs Messages

Page history last edited by Glenn Block 11 years, 9 months ago



  • Deciding Entity vs Message relates all the way to how we display the data to the user.
    • Concurrency - do we care about if one user overlaps another data? Is last one  / first one wins? Or do we need to perform a union?
  • Losing the context of what the user was doing.
    • If a user is modifying some data in the UI, how do I know what was going on?
      • How do we validate?
      • How do we check concurrency?
    • How does the user express intent of what they are doing?
    • Task driven UI model necessary.


  • Without having a task based application, all the messages in the world do not matter.
  • Messaging necessary for occasionally connected apps in order to properly execute business logic / validation on the server


Comments (0)

You don't have permission to comment on this page.