Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
CardSync Web App Package
The basic idea of CardSync Web App Package is to keep the state of the user's data structures in RPPS Package in sync with the N copies of the user's data structures that exist on N separate client selectors (e.g. on the user's computers and mobile devices). Changes made by the user directly in RPPS Package (e.g. via the Cloud Selector or a thin client selector such as the AIR Selector 1.1-Win) need to be propagated to the user's N fat client selectors. Also, changes made on any one of these N fat clients should be synchronized to the other N-1 devices/computers and to RPPS Package
- CardSync Synchronization - Synchronization algorithm
- CardSync_JAX-RS_API - CardSync API
- Persona Data Mode1 1.0 - the existing data model
- Persona Data Model 1.1 is a new revision of the data model under development for data used by the RPPS Package "application"
The following diagram provides more details; it shows interconnections between sub-components (called components in this diagram) between components shown above: