Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

CardSync Web App Package

{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}

Higgins logo 76Wx100H.jpg

Web app that implements the CardSync Service. See also CardSync Closed Design Issues.

Version

org.eclipse.higgins.cardsync.web is being developed as part of Higgins 1.1.

Implementation

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

Architecture

The following diagram provides more details; it shows interconnections between sub-components (called components in this diagram) between components shown above:

CardSyncComponentDiagram.png

Back to the top