Skip to main content
Jump to: navigation, search

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]]
=== Design Goals ===
+
 
Here are the original design goals for the [[CardSync Web App]]:
+
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}}

Higgins logo 76Wx100H.jpg

Original design goals for the CardSync Service:

  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