All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Harald Schmitt <linux@hschmitt.de>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 0/2] obexd: Fix bug in irmc phonebook and prevent to reintroduce it
Date: Fri, 27 Jul 2012 16:40:42 +0300	[thread overview]
Message-ID: <CABBYNZ+9qc4v3kW1gLVo4SHb924z+WXT8V8wTFAvW3hT6gZhYQ@mail.gmail.com> (raw)
In-Reply-To: <50100AB5.8050203@hschmitt.de>

Hi Harald,

On Wed, Jul 25, 2012 at 6:03 PM, Harald Schmitt <linux@hschmitt.de> wrote:

>> While the backend indeed take an absolute path this doesnt mean we
>> have to send as absolute path, not to mention it is not compatible
>> with mimetypes which is what TYPE header describes, even in case of
>> PBAP it is wrong to send absolute path in SETPATH.
>
> Patch 1/2 only changes the way phonebook_pull is called (with absolute
> path). It has nothing changed about the path resolution/interpretation
> that is asked from the client. Sorry for my bad explanations.

Yep, only now I realized that this is not the client side, so it is
probably fine.

>>
>> To avoid this problems we send relative although we do accept
>> absolute, but to avoid problems with stack interpreting absolute path
>> as not valid as OBEX spec state we always send relative paths.
>
> In fact irmc implementation at the moment only accepts relative paths
> and I did not change this.

No problem, I will make it less strict to follow PBAP in another patch.

>>
>>> The patch 1/2 fixes irmc to query phonebook implementation for the well
>>> known absolute path. This was changed in pbap.c with the patch you
>>> stated, but forgot to change in irmc.c.
>>> Patch 2/2 just replaces the well-known phonebook paths which
>>> phoenbook-ebook.c and phonebook-tracker.c support with constants.
>>
>> Im fine with converting to constants, it is more the sending of
>> absolute path that Im not comfortable because of the potential
>> interoperability problems it could cause.
>
> I probably used the wrong term "well known" what I meant by well known
> are the paths that phonebook-tracker and phonebook-ebook knows that it
> should fetch the contacts, etc. and these are absolute paths. It is not
> about the "well known" paths from the pbap spec

No problem, I should have looked what the code was doing before
drawing any conclusion, anyway I will apply this patches asap.


-- 
Luiz Augusto von Dentz

  reply	other threads:[~2012-07-27 13:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-18 14:53 [PATCH 0/2] obexd: Fix bug in irmc phonebook and prevent to reintroduce it Harald Schmitt
2012-07-18 14:53 ` [PATCH 1/2] irmc: Fix phonebook contacts query Harald Schmitt
2012-07-18 14:53 ` [PATCH 2/2] phonebook: Replace magic strings for phonebook names and folders Harald Schmitt
2012-07-24 20:20 ` [PATCH 0/2] obexd: Fix bug in irmc phonebook and prevent to reintroduce it Luiz Augusto von Dentz
2012-07-25  7:18   ` Harald Schmitt
2012-07-25 14:22     ` Luiz Augusto von Dentz
2012-07-25 15:03       ` Harald Schmitt
2012-07-27 13:40         ` Luiz Augusto von Dentz [this message]
2012-07-27 15:07           ` Luiz Augusto von Dentz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CABBYNZ+9qc4v3kW1gLVo4SHb924z+WXT8V8wTFAvW3hT6gZhYQ@mail.gmail.com \
    --to=luiz.dentz@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux@hschmitt.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.