Places/AsyncAPIsForSync: Difference between revisions

Jump to navigation Jump to search
m
Line 229: Line 229:


Don't have a strong preference.  I say just defer to sr on this.  --sdwilsh
Don't have a strong preference.  I say just defer to sr on this.  --sdwilsh
Dietrich suggested to just do a AsyncBookmarks.jsm module, and completely drop xpcom. I mostly agree, this interface is not going to have cpp users, and we are also making it hard for cpp users (the arrays and so on...). We'd just need some private interface in nsPIPlacesDatabase to forward notifications.  What would block us from doing that? --mak


=== Parent Name===
=== Parent Name===
Confirmed users
595

edits

Navigation menu