This demonstration took E4 modeled UI and stored it in CDO. Multiple clients were started, and connected to CDO. When the UI of one instance was updated, all of the other ones followed.
CDO stores the EMF objects. When an object changed, an event was sent to update the UI as well as to update the CDO data store. CDO then forwards the event to other clients of the store, each of which update their UIs with the changes.
By using CDO's temporal functionality, the changes could be reversed and re-applied, and all of the listening UIs would react to the changes.
CDO (Connected Data Objects) can be though of as a run-time persistence platform for models, and provides many features:
- Multi-user access
- Transactios
- Transparent temporality
- Parallel evolution
- Scalability
- Thread safety
- Collaboration
- Data integrity
- Fault tolerance
- Offline work
The demo was an impressive display of how flexible E4 with EMF and CDO are, and opens up a lot of potential use cases for the technology such as:
- Workspace in the cloud
- Preconfigured perspectives
- Central preference store
- Kiosk Applications
- Instant provisioning
- Pair, or more, programming UIs
- Code reviewing application
- Multi-user graphs
- etc.
No comments:
Post a Comment