On Mon, 2014-11-17 at 12:58 +0200, Von Dentz, Luiz wrote:
> 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,

SyncEvolution needs to talk to something which does the actual PBAP
transfer for it. Currently that's obexd via the obexd D-Bus API. As I
pointed out, using CAPI instead doesn't seem to be an option at the
moment.
 
This might be changed, but before investing work into that (both in NTB
and SyncEvolution), I'd like to hear a convincing argument why that
would be a better solution overall.

How multi-user support gets implemented is part of the bigger picture.

>  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.

Crosswalk uses a Tizen-specific native component, the phoned, which
talks to obexd via D-Bus. It's in the same situation as SyncEvolution.
Long term I think the contact handling in phoned should get replaced
with SyncEvolution's, but for now support both approaches in Tizen.

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.



_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev

Reply via email to