IdAS Update Proposals Committed Updates

This is similar to Option #2, except that we introduce a commit method where appropriate. This allows the consumer to perform unnecessary add/delete operations on data elements and follow it with a commit method. No changes are applied to the backing data until the commit method is called, and when it is called, all updates are committed as an atomic operation.

• Pros
  • Still easy for the consumer
  • Single commit operation triggers updates to happen as an atomic operation
• Cons
  • CP implementation must keep track of what's being updated until the commit method is called.
  • As in option #2, consumer still unsure to which objects a commit will be applied. This must be resolved.