Hi Zoltan, DataStore affects Messaging Api too. All operations for sms/mms by ContentProvider are replaced by it. Add It's not clear if message send/receive events are handled by it, also. That's a totally change. If DataStroe is ready, only Javascript side coding is required to implement Messaging API.
Thanks, Shawn -----Original Message----- From: Crosswalk-dev [mailto:crosswalk-dev-boun...@lists.crosswalk-project.org] On Behalf Of Huang, Deqing Sent: Wednesday, November 13, 2013 3:56 PM To: Kis, Zoltan Cc: crosswalk-dev@lists.crosswalk-project.org Subject: Re: [Crosswalk-dev] Intent to Implement: [Android] W3C SysApps Contacts API Hi Zoltan, Thanks for the reply. A quick question: is DataStore API efficient for Contacts on Android? Unlike FxOS, it is possible that the address book be modified by other apps on Android, while not through WebAPI. I guess in this case DataStore API must sync with address book, so that the current application which using Contacts API can keep its UI up-to-date. Will the DataStore API cover this and how to keep it efficient? Regards, Deqing -----Original Message----- From: Kis, Zoltan [mailto:zoltan....@intel.com] Sent: Tuesday, November 12, 2013 9:05 PM To: Huang, Deqing Cc: Kenneth Rohde Christiansen; crosswalk-dev@lists.crosswalk-project.org Subject: Re: [Crosswalk-dev] Intent to Implement: [Android] W3C SysApps Contacts API Sorry for the late answer, I was busy with the Telephony & Messaging API and SysApps F2F on TPAC. Yes, I am in the loop with the Contacts API, but I am not editor. The outstanding question since the last F2F (August) is whether to use DataStore API for Contacts and Messaging (and CallHistory). https://wiki.mozilla.org/WebAPI/DataStore Mozilla is really pushing for it. That is useful in an FxOS type environment, but not very efficient for Tizen... In August I have made drafts for each spec above, using DataStore, and it indeed simplifies the spec itself - but we have serious doubts about being able to implement it efficiently, with Tizen native story in mind, too. http://lists.w3.org/Archives/Public/public-sysapps/2013Aug/0077.html I sketched the problem wrt CallHistory, which is partly similar story, check this: https://github.com/sysapps/telephony/issues/212 Tomorrow we will have a conference call with Mozilla and Telefonica about DataStore. I will send an update about the decision, if we reach any. Until this is settled, you can still work on the API parts that are not affected by DataStore. Check this draft (also mentioned in the sysapps mail link from above): https://etherpad.mozilla.org/R2Xrl2253o Best regards, Zoltan On Mon, Nov 11, 2013 at 10:06 AM, Huang, Deqing <deqing.hu...@intel.com> wrote: > Status of the Spec: > > Editor’s draft, as indicated in > http://www.w3.org/2012/sysapps/contacts-manager-api/ > > Not sure if Anssi, Sakari or Zolton knows more details of the status? > > > > Support from other venders: > > AFAIK Firefox Mobile(Gecko) supports this API since 18.0 > > Not supported on Android, Opera, Safari, Chrome, and Firefox desktop. > > > > Compatibility Risk: > > Low. This is a new feature, which implemented as an individual > internal extension. > > > > Regards, > > Deqing > > > > From: Kenneth Rohde Christiansen > [mailto:kenneth.christian...@gmail.com] > Sent: Friday, November 08, 2013 6:48 PM > To: Huang, Deqing > Cc: crosswalk-dev@lists.crosswalk-project.org; Kis, Zoltan > Subject: Re: [Crosswalk-dev] Intent to Implement: [Android] W3C > SysApps Contacts API > > > > Sorry, Zoltan is for the messaging parts, not Contacts - but I bet he > knows about the status as well :-) > > > > On Fri, Nov 8, 2013 at 11:46 AM, Kenneth Rohde Christiansen > <kenneth.christian...@gmail.com> wrote: > > This intent doesn't speak about the status of the spec, support from > other vendors, the risks involved with implementing etc. > > > > Please look at blink-dev for how to write proper intents (which > includes all of these things). > > > > The above is really what I want to know about before giving the > initial green light. > > > > Zoltan, are you are the owner of this spec, can you share some light > and also does the implementation plan sound good to you? > > > > Cheers > > Kenneth > > > > On Fri, Nov 8, 2013 at 8:18 AM, Huang, Deqing <deqing.hu...@intel.com> > wrote: > > Description: This implemented W3C Contacts Manager API on Android > > Affected component: N/A > > Related feature: XWALK-49 > > Target Release: Crosswalk M4 > > > > Implementation details: > > > > Spec: http://www.w3.org/2012/sysapps/contacts-manager-api/ > > > > Summary: > > This API is designed as an internal extension based the > XWalkExtensionBridge. > > > > JSAPI part: > > Promise will be used as per spec indicates. This Promise interface > would be the same as other extensions which also has Promise defined in their > specs. > > > > Java part: > > Most operations are based on Content Provider, which is, using > ContentResolver to access and modify system's Contact data table as > required. There are several major parts described below: > > 1> For saving or updating a contact, will build an array list of > ContentProviderOperation and apply to the system's contact table in > batch in order to increase performance. > > 2> For finding a contact, will construct a SQL clause by find option > 2> to > query contact data table and build results to JSON string to post back > to caller. Similarly when removing one or more contacts, will > construct a SQL selection clause to delete rows of contact data table. > > 3> For message handler of Contacts change, will register a Content > 3> Observer > to listen change of contact data table by ContentResolver. > > > > Regards, > > Deqing > > > > > > > > > > _______________________________________________ > Crosswalk-dev mailing list > Crosswalk-dev@lists.crosswalk-project.org > https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev > > > > > > -- > Kenneth Rohde Christiansen > Web Platform Architect, Intel Corporation. > Phone +45 4294 9458 ﹆﹆﹆ > > > > > > -- > Kenneth Rohde Christiansen > Web Platform Architect, Intel Corporation. > Phone +45 4294 9458 ﹆﹆﹆ _______________________________________________ Crosswalk-dev mailing list Crosswalk-dev@lists.crosswalk-project.org https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev _______________________________________________ Crosswalk-dev mailing list Crosswalk-dev@lists.crosswalk-project.org https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
