Services/Sync/WEP/116: Difference between revisions

Jump to navigation Jump to search
 
Line 131: Line 131:
From this it's pretty clear that the store interface needs to become async. It's ''probably'' going to be ok to do this without backwards compatibility as the store is only in during SyncEngine.sync() and its helpers. Unless of course we care about third party implementations.  
From this it's pretty clear that the store interface needs to become async. It's ''probably'' going to be ok to do this without backwards compatibility as the store is only in during SyncEngine.sync() and its helpers. Unless of course we care about third party implementations.  


We might need to turn places annotations (<tt>Utils.anno()</tt>) into DB queries as well, at which point the Bookmarks and History trackers would be using <tt>Utils.queryAsync()</tt> as well. However, since trackers are often invoked async anyway (as observers for places/satchel/... notifications), we could just as easily make that fully async.<br>  
We might need to turn places annotations as returned by <tt>Utils.anno()</tt> into async DB queries as well (see {{bug|584927}}), at which point the Bookmarks and History trackers would be using <tt>Utils.queryAsync()</tt> too. However, since trackers are often invoked async anyway (as observers for places/satchel/... notifications), we could just as easily make that fully async.<br>


=== Things that use <tt>Svc.Crypto</tt>: ===
=== Things that use <tt>Svc.Crypto</tt>: ===
canmove, Confirmed users
725

edits

Navigation menu