canmove, Confirmed users
640
edits
CloudServices/Sync/FxSync/FaviconSync: Difference between revisions
CloudServices/Sync/FxSync/FaviconSync (view source)
Revision as of 21:25, 29 July 2011
, 29 July 2011→Questions/Observations
| Line 100: | Line 100: | ||
*How should we model the expiration (if at all)? | *How should we model the expiration (if at all)? | ||
*How to access favicon data? Raw SQL r+w? Extend mozIAsyncHistory? | *How to access favicon data? Raw SQL r+w? Extend mozIAsyncHistory? | ||
** mozIAsyncFavicons. | ** mozIAsyncFavicons. This API is ours to chop up and extend, with appropriate judgment. | ||
*How can we be notified when a new favicon is added or an existing one is changed? | *How can we be notified when a new favicon is added or an existing one is changed? | ||
** Observers. See above. | ** Observers. See above. | ||
* How do we tie into or interact with Places' favicon expiration events? | * How do we tie into or interact with Places' favicon expiration events? | ||
* It would seem to make sense to sync favicons before bookmarks, so as to have favicons present in the DB before they are linked to their bookmark record. We should also take care to keep toolbar/menu icons very much in the working set: synced first, and generally given priority. UX über alles! | * It would seem to make sense to sync favicons before bookmarks, so as to have favicons present in the DB before they are linked to their bookmark record. We should also take care to keep toolbar/menu icons very much in the working set: synced first, and generally given priority. UX über alles! | ||