Return-Path: MIME-Version: 1.0 In-Reply-To: <1345707325.29868.403.camel@pohly-mobl1.fritz.box> References: <1345651474.29868.344.camel@pohly-mobl1.fritz.box> <1345707325.29868.403.camel@pohly-mobl1.fritz.box> Date: Thu, 23 Aug 2012 11:15:48 +0300 Message-ID: Subject: Re: PBAP + two-step download From: Luiz Augusto von Dentz To: Patrick Ohly Cc: Bluez , Mikel Astiz , Jeremy Whiting Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Hi Patrick, On Thu, Aug 23, 2012 at 10:35 AM, Patrick Ohly wrote: > On Thu, 2012-08-23 at 01:13 +0300, Luiz Augusto von Dentz wrote: >> Hi Patrick, >> >> On Wed, Aug 22, 2012 at 7:04 PM, Patrick Ohly wrote: >> > Hello! >> > >> > For IVI use cases, Mikel and I were discussing how a phone's address >> > book could be cached intelligently by an IVI head unit. The rough idea >> > is that first all contacts get pulled without PHOTO data. This data is >> > used to match the current phone address book with some potentially >> > cached local data. Then in a second step, the PHOTO data of all contacts >> > is requested (*). This is all done in the same PBAP session, so the >> > numbering of contacts is the same in both steps. >> > >> > The goal is to get the essential data (names, phone numbers) quickly and >> > then add pictures later on. >> >> I think it is a good idea, but what about to download the full contact >> vcard only when it is to be displayed? > > There are other use cases that depend on having all data locally, for > example merging address books from several different phones into a > single unified address book. Browsing that unified address book is > expected to include photo data, so loading that on demand isn't an > option. How you deal with conflicts such as different pictures, names for the same contact? In theory merging seems to be the right thing to do but if you have used e.g. Nokia N9 it can cause many problems where the same phone number can be found in multiple contacts. What if we got in a situation where the IVI system show 'Joe' but the phone shows "John" with a different picture, I guess this is supposed to be consistent with the phone that is handling the call. > What you describe is part of the plan, as fallback when the data is not > (yet) available locally. > >> When we connect we attempt to >> download the full phonebook which is cached for fast lookup but while >> ringing we can download the full vcard including the picture. > > Even if we wanted to do it that way, it also wouldn't work at the moment > because the PullAll download doesn't include the information that is > necessary to get the full vcard later on. Any comments about my > proposals for fixing this (download into dir and/or add X- prop to > vcards)? What about Search + Pull? If you have download the contact already you have the name then you search by name, otherwise search by number, with the response you can download the vcard with Pull. Btw, Im changing the PhonebookAccess API so the parameters like order, format and filter is passed in the same method call so the client doesn't have to call multiple methods for setting those. -- Luiz Augusto von Dentz