Hi Patrick, On Mon, Nov 17, 2014 at 10:30 AM, Patrick Ohly <[email protected]> wrote: > On Fri, 2014-11-14 at 22:51 +0000, Xu, Martin wrote: >> Hi Kis: >> Thanks for your comments on NTB, and in general, we have same opinions from >> technology. >> Please see my comments. >> > The bigger problem is that CAPI [1] does not support the features promised >> > in the architecture slides [2], so it is impossible to be used in Crosswalk >> > extensions using PBAP and MAP for instance. Instead we need to directly use >> > BlueZ, and that is what I am doing now. >> Please tell me detail what is the features promised in CAPI and not >> supported? >> And what is the detail about why you can't use PBAP and MAP? > > Because PBAP is not part of the CAPI? See also my email from October > 29th that no-one replied to: > http://permalink.gmane.org/gmane.comp.handhelds.tizen.devel/4677
Btw, perhaps PBAP does not need to be part of the CAPI if syncevolution API provides the same functionality, but I guess that would mean synchronizing missed calls, etc, which I guess syncevolution currently ignores. Regarding Crosswalk I would have guessed it would make sense to just use D-Bus directly so it would work with any platform using BlueZ, if that is not possible in Tizen then we have the same problems listed bellow. >> So here I want to introduce another design goal of NTB: >> All the Bluetooth service should go through the unified interface. Of course >> Best option is to use BlueZ dbus interface. But during past 6 years working >> on >> Comms projects like (BlueZ/ConnMan/oFono). I got to know that it is not easy >> to use Dbus. > > That may have been your experience. I'd rather use a D-Bus API directly > instead of having to go through some "simplified" layer on top which > prevents doing all the things that can be done with the underlying API. Not only it may restrict the features exposed it also creates a build time dependency. >> I do not know what is your meaning of full functionality support in CAPI? >> >> From the wiki page you should know that we have passed TCT test pass rate >> 98.13%(322 test case and 314 passed) > > You pass the tests that Samsung defined for the functionality that was > need for the Mobile profile. The tests for the missing functionality > haven't been written, so arguing based on pass rates is pretty > pointless. +1 _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
