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.
Difference between revisions of "CardSync Service 1.1"
(→Version) |
(→Implementation Architecture) |
||
Line 25: | Line 25: | ||
* The [[CardSync Service]] will be first used by the [[GTK Selector 1.1-Win]] solution. It is used by the Synchronizing Card Store within the [[Local I-Card Service]]. | * The [[CardSync Service]] will be first used by the [[GTK Selector 1.1-Win]] solution. It is used by the Synchronizing Card Store within the [[Local I-Card Service]]. | ||
− | |||
− | |||
− | |||
− | |||
===Components and Packages=== | ===Components and Packages=== |
Revision as of 09:41, 12 July 2009
{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}
The CardSync Service is a web service that synchronizes card data between itself and one or more selector clients. Changes made on any one of a user's selectors are synchronized to all of the other of that user's selectors.
Version
The CardSync Service is being developed as part of Higgins 1.1.
API
- CardSync JAX-RS API - RESTful API
- CardSync Authentication - RESTful API Authentication
- CardSync Exceptions - coming soon
- CardSync Data Transfer Objects - objects moving over the network
Design Requirements
Here are the original design goals for the CardSync Web App:
- Support a RESTful interface (not SOAP)
- Only use protocols and technologies that are available royalty-free and are well documented
- Be compatible with selectors that support N>1 card stores
- Allow a selector to work completely offline
- Support bi-directional synchronization of individual cards and individual metadata entries about these cards
- Support strong authentication from client (selector) to CardSync Service
Used By
- The CardSync Service will be first used by the GTK Selector 1.1-Win solution. It is used by the Synchronizing Card Store within the Local I-Card Service.
Components and Packages
Components:
Packages: