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 Design Goals"
(New page: {{#eclipseproject:technology.higgins|eclipse_custom_style.css}} right === Design Goals === Here are the original design goals for the [[CardSync Web App...) |
|||
| Line 1: | Line 1: | ||
{{#eclipseproject:technology.higgins|eclipse_custom_style.css}} | {{#eclipseproject:technology.higgins|eclipse_custom_style.css}} | ||
[[Image:Higgins_logo_76Wx100H.jpg|right]] | [[Image:Higgins_logo_76Wx100H.jpg|right]] | ||
| − | + | ||
| − | + | Original design goals for the [[CardSync Service]]: | |
# Support a RESTful interface (not SOAP) | # Support a RESTful interface (not SOAP) | ||
# Only use protocols and technologies that are available royalty-free and are well documented | # Only use protocols and technologies that are available royalty-free and are well documented | ||
Latest revision as of 09:55, 12 July 2009
{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}
Original design goals for the CardSync Service:
- 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