Confirmed users
595
edits
Places/AsyncAPIsForSync: Difference between revisions
Jump to navigation
Jump to search
→Predecessor
m (→Interfaces) |
|||
| Line 254: | Line 254: | ||
Both option 1 and 3 would mean a version bump for the bookmark storage. These are similarly problematic as global storage version bumps. Fortunately, we're doing one very very soon, so we could just move to the new bookmark storage version now so that it's in place when we get the async APIs. | Both option 1 and 3 would mean a version bump for the bookmark storage. These are similarly problematic as global storage version bumps. Fortunately, we're doing one very very soon, so we could just move to the new bookmark storage version now so that it's in place when we get the async APIs. | ||
I'm personally leaning towards option 3 --philikon | I'm personally leaning towards option 3 --philikon | ||
Changing bookmarks table to drop position could not be that easy, I have to check, but iirc we rely pretty much on that positioning and on it not having "holes". So if that's the idea, we have to be cautious here, if the "bookmark storage" is something on Sync side, then nevermind! --mak | |||
=== Tags === | === Tags === | ||