Imagine the following reasonable app scenario:
- Simultaneous data changes occur across several UI components
- Those data changes may be caused by local, mostly user initiated events
- Or they may be caused by "remote" events, originating from collaboration; and propagated via SmartClient's messaging solution, for example
- And last, but not least: It shall be possible to commit OR cancel/rollback those simultaneous data changes across all impacted UI components
What is SmartClient's approach to handle such a scenario ? Which has the "smell" of needing some form of client-side transaction management ?
- Simultaneous data changes occur across several UI components
- Those data changes may be caused by local, mostly user initiated events
- Or they may be caused by "remote" events, originating from collaboration; and propagated via SmartClient's messaging solution, for example
- And last, but not least: It shall be possible to commit OR cancel/rollback those simultaneous data changes across all impacted UI components
What is SmartClient's approach to handle such a scenario ? Which has the "smell" of needing some form of client-side transaction management ?