Places:Sync: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
== Active Work == | |||
Bugs: | |||
* {{bug|374518}} - Platform support | |||
* {{bug|374519}} - Sync client | |||
== Goals == | == Goals == | ||
P1: | P1: | ||
* | * Provide the platform-level support required for sync extensions | ||
P2: | P2: | ||
* sync bookmarks hierarchy | * Sync Client | ||
* sync tag data | ** sync bookmarks hierarchy | ||
** sync tag data | |||
== Requirements == | == Requirements == | ||
Revision as of 21:39, 13 June 2007
Active Work
Bugs:
- bug 374518 - Platform support
- bug 374519 - Sync client
Goals
P1:
- Provide the platform-level support required for sync extensions
P2:
- Sync Client
- sync bookmarks hierarchy
- sync tag data
Requirements
- all bookmark and tag data must by sync-able.
- client api should allow server-dictated external authentication mechanisms, such as HTTP auth or browser-based auth.
- client api should allow extension data attached to bookmarks/folders/tags be synced as well (maybe just through annotations?).
should support the following scenarios:
- initial: client has data, server has none
- client changes: client has changes, server has no changes
- server changes: server has changes, cient has none
- concurrent overlapping: same item changed on both client and server
- concurrent non-overlapping: different items changed on both client and server
Design
Implementation
- XXX provide info about sayrer's sync.js
Open Issues
- sync all item annos?
- security review of json on-the-wire, eval sandbox