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 "Org.eclipse.higgins.cardsync.web"
| Line 2: | Line 2: | ||
[[Image:Higgins_logo_76Wx100H.jpg|right]] | [[Image:Higgins_logo_76Wx100H.jpg|right]] | ||
| − | Web app that implements the | + | Web app that implements the [[CardSync Service]]. |
=== Version === | === Version === | ||
Revision as of 10:07, 12 July 2009
{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}
Web app that implements the CardSync Service.
Contents
Version
org.eclipse.higgins.cardsync.web is being developed as part of Higgins 1.1.
Implementation
- CardSync Synchronization - Synchronization process
Architecture
The following diagram provides more details; it shows interconnections between sub-components (called components in this diagram) between components shown above:
Closed Issues
Should we use WebDAV?
Reasons For:
- reduces our development effort as this protocol is designed for resource synchronization. And that's what we're doing
- mature, widely supported. Being used in new projects such as Mozilla Weave.
Reasons Against:
- Not RESTful. WebDAV extends the HTTP verb set. As such is deprecated by the W3C.
- Can interfere with web cache architectures
Decision:
- We will NOT use WebDAV
Should we use Google protocol buffers?
Reasons For:
- Mature
- High performance
- Good libraries in both C++ and Java
Reasons Against:
- Question: Might using protobuf reduce the likelyhood of the CardSpace team collaborating with us and potentially using the CardSync Web App? <-- an outcome that would increase interoperability in the industry
Decision:
- We will NOT use Google protocol buffers