Services/Sync/WEP/116: Difference between revisions

Services/Sync/WEP/116 (view source)

1,020 bytes added , 27 September 2010

canmove, Confirmed users

725

edits

@@ Line 19: / Line 19: @@
 <br>
-Things that use Resource:<br>
+#Everything takes a callback<br>
+== Task overview ==
+<br>
+Things that use <tt>Resource</tt>:<br>
 {| cellspacing="1" cellpadding="1" border="1"
 |-
-! scope="col" | API Method<br>
+! scope="col" | Method<br>
 ! scope="col" | Risk<br>
 ! scope="col" | Used where (big picture)<br>
@@ Line 100: / Line 106: @@
 <br>
+Things that use <tt>Utils.queryAsync()</tt>:<br>
+{| cellspacing="1" cellpadding="1" border="1"
+|-
+! scope="col" | API Method<br>
+! scope="col" | Comment
+|-
+| BookmarksStore.update()
+| <br>
+|-
+| FormStore.getAllIDs(), FormStore.createRecord(), FormStore.remove(), FormStore.itemExists(), FormStore.changeItemID()
+| all via FormTracker<br>
+|-
+| FormTracker.trackEntry()
+| via FormTracker<br>
+|-
+| FormEngine._findDupe()
+| via FormTracker<br>
+|-
+| HistoryStore._haveTempTables, HistoryStore.update(), HistoryStore.createRecord(), HistoryStore.changeItemID(), HistoryStore.remove(), HistoryStore.itemExists(), HistoryStore.getAllIDs()
+| <br>
+|}
 <br>
-<br>
+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.
-#Everything takes a callback<br>
 <br>