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.
Difference between revisions of "CardSync Service 1.1"
(→Implementation) |
|||
| Line 7: | Line 7: | ||
The [[CardSync Service]] is being developed as part of [[Higgins 1.1]]. | The [[CardSync Service]] is being developed as part of [[Higgins 1.1]]. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Here are the original design goals for the [[CardSync Web App]]: | Here are the original design goals for the [[CardSync Web App]]: | ||
# Support a RESTful interface (not SOAP) | # Support a RESTful interface (not SOAP) | ||
| Line 21: | Line 14: | ||
# Support bi-directional synchronization of individual cards and individual metadata entries about these cards | # Support bi-directional synchronization of individual cards and individual metadata entries about these cards | ||
# Support strong authentication from client (selector) to [[CardSync Service]] | # Support strong authentication from client (selector) to [[CardSync Service]] | ||
| + | |||
| + | == Service == | ||
| + | === API === | ||
| + | * [[CardSync JAX-RS API]] - RESTful API | ||
| + | |||
| + | === Misc === | ||
| + | * [[CardSync Authentication]] - RESTful API Authentication | ||
| + | * [[CardSync Exceptions]] - coming soon | ||
| + | * [[CardSync Data Transfer Objects]] - objects moving over the network | ||
=== Used By === | === Used By === | ||
Revision as of 09:47, 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.
Contents
Version
The CardSync Service is being developed as part of Higgins 1.1.
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
Service
API
- CardSync JAX-RS API - RESTful API
Misc
- CardSync Authentication - RESTful API Authentication
- CardSync Exceptions - coming soon
- CardSync Data Transfer Objects - objects moving over the network
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.
Implementation
Architecture
(Diagram Key) Italic text
Components and Packages
Components:
Packages: