desktopcouch improvements
Registered by
John Lenton
how can we make desktopcouch better in maverick, and what problems did users run into in lucid? What sorts of data and what sorts of loads is desktopcouch suited for? Gwibber is an obvious example here.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Whiteboard
= APIs to add =
* DB compaction
* D-Bus changes API
* Remove pseudo-delete in desktopcouch
Work Items:
[benoitc] patch to have Couch tell you which port it is on: TODO
[chipaca] research how best to push D-Bus change notifications (push all the time for every db?): TODO
[chipaca] D-Bus API for change notifications for couch: TODO
[chipaca] investigate moving to couchdbkit rather than couchdb-python (must be done before alpha2): TODO
[chipaca] port cloud_server improvements back into desktopcouch: TODO
(?)
