User:P.A./Download architecture improvements: Difference between revisions

→‎Initial implementation: Clarify that downloads history is stored in the Places database
m (Fix link)
(→‎Initial implementation: Clarify that downloads history is stored in the Places database)
 
Line 39: Line 39:
# Get JSON serialization in place, working as a Downloads Panel back-end
# Get JSON serialization in place, working as a Downloads Panel back-end
# Implement nsIDownloadManager / nsIDownload compatibility (conversion of download states, synchronous control functions, ...)
# Implement nsIDownloadManager / nsIDownload compatibility (conversion of download states, synchronous control functions, ...)
# Implement an import path for downloads.sqlite (no need to export, since downloads are per session, and on downgrade the download history will not be lost, only paused downloads will be lost)
# Implement an import path for downloads.sqlite (no need to export, since downloads are per session, and on downgrade the download history will not be lost (it's stored in the Places database), only paused downloads will be lost)


== Complete design ==
== Complete design ==
Confirmed users
183

edits