CloudServices/Sync/FxSync/ClientPriorities: Difference between revisions
< CloudServices | Sync | FxSync
Jump to navigation
Jump to search
| Line 11: | Line 11: | ||
* (P1) War On Sync | * (P1) War On Sync | ||
** Don't spin the event loop | ** Don't spin the event loop {{bug|600059}} | ||
*** Introduce async APIs | *** Introduce async APIs across SyncEngine, Store, Tracker | ||
*** also see [[/Services/Sync/WEP/116]] | *** also see [[/Services/Sync/WEP/116]] | ||
** Avoid synchronous I/O *everywhere*. Needs async bulk APIs in platform: | ** Avoid synchronous I/O *everywhere*. Needs async bulk APIs in platform: | ||
| Line 33: | Line 33: | ||
** use Services, XPCOMUtils where possible | ** use Services, XPCOMUtils where possible | ||
** use NetUtil.BadCertHandler? | ** use NetUtil.BadCertHandler? | ||
** implement + use toolkit generic async resource | ** implement + use toolkit generic async resource {{bug|581560}} | ||
* (P3) Automatic Profiling | * (P3) Automatic Profiling | ||
Revision as of 01:16, 10 March 2011
Firefox Sync client engineering roadmap
Features
- (P2) Push to mobile
- (P2) Sync add-ons
- (P2) Sync web apps
- (P2) Sync localStorage
Platform
- (P1) War On Sync
- Don't spin the event loop bug 600059
- Introduce async APIs across SyncEngine, Store, Tracker
- also see /Services/Sync/WEP/116
- Avoid synchronous I/O *everywhere*. Needs async bulk APIs in platform:
- forms
- passwords
- bookmarks
- Don't spin the event loop bug 600059
- (P1) Crossweave 2.0
- lives in services/sync/tests/...
- maintained by us, run by tinderboxes
- mochitests? mozmill?
- JSON test file format (avoid custom format + parser), possibly even JS
- moar end-to-end tests
- tests the hell out of bookmark dupe detection
- test all obscure bookmark types (queries, etc.)
- need to test errors and edge cases as well
- run on fennec
- (P2) Get rid of 3.5/3.6 compat code
- use Services, XPCOMUtils where possible
- use NetUtil.BadCertHandler?
- implement + use toolkit generic async resource bug 581560
- (P3) Automatic Profiling
- are we JITing everywhere?
- main thread blocking (UI responsiveness)
- memory leaks