On Wed, Nov 27, 2013 at 8:17 AM, Gao, Shawn <[email protected]> wrote: > + Anssi & Sakari > > _____________________________________________ > From: Gao, Shawn > Sent: Wednesday, November 27, 2013 2:14 PM > To: Kis, Zoltan; [email protected] > Cc: Huo, Halton > Subject: Messaging.findConversations() > > > Hi Zoltan, > Messaging have an api definition, “Promise findConversations (DOMString > groupBy, MessagingFilter filter, FilterOptions options);”. And, > MessageFilter have attributes like startDate and endDate, but no thread_id. > If no thread_id, startDate and endDate are useless. Because nobody will > search all conversations between two time points. I suggest add thread_id > to arguments of findConversations().
Makes sense to me. This API was a result of a long fight with Telefonica, so I need to ask them. However, the whole point is made moot by the DataStore discussion. We have some reserves against the DataStore idea, and would like to hear your opinion as an implementor. What do you think, what is better for app developers: - an API like the current Messaging with find() method, or - sync data from the system to the app local cache (e.g. an IndexedDB), and build the indexes the app wants? The second is likely easier to implement, but harder to use, - well, with more control for the app developer, too. Thanks, Zoltan _______________________________________________ Crosswalk-dev mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
