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 Design Goals

Revision as of 09:54, 12 July 2009 by Ptrevithick.gmail.com (Talk | contribs) (New page: {{#eclipseproject:technology.higgins|eclipse_custom_style.css}} right === Design Goals === Here are the original design goals for the [[CardSync Web App...)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

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

Higgins logo 76Wx100H.jpg

Design Goals

Here are the original design goals for the CardSync Web App:

  1. Support a RESTful interface (not SOAP)
  2. Only use protocols and technologies that are available royalty-free and are well documented
  3. Be compatible with selectors that support N>1 card stores
  4. Allow a selector to work completely offline
  5. Support bi-directional synchronization of individual cards and individual metadata entries about these cards
  6. Support strong authentication from client (selector) to CardSync Service

Back to the top