On Wed, Nov 27, 2013 at 8:17 AM, Gao, Shawn <[email protected]> wrote: > 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().
Basically people wanted to hide thread_id as a persistent property, since it is app dependent how to define a thread. Instead, they wanted the 'groupBy' parameter, which can identify threads, which then the app will save to its own database, together with the message id's belonging to it. I understand that may not be an optimal assumption. What do you think, should I press on having an opaque conversationId? (I used to have it in my proposals, but was removed). Thanks, Zoltan _______________________________________________ Crosswalk-dev mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
