Linux bluetooth development
 help / color / mirror / Atom feed
From: Hendrik Sattler <post@hendrik-sattler.de>
To: linux-bluetooth <linux-bluetooth@vger.kernel.org>
Subject: Re: [RFC] API for MAP client in obex-client
Date: Thu, 03 Nov 2011 14:52:15 +0100	[thread overview]
Message-ID: <9a761ff17e9379d239fb223e2bc4440f@mail.hendrik-sattler.de> (raw)
In-Reply-To: <CAPGrrxXkvaNjnUT9vJ8sdnHuabF7zwtWnOnnbLD1+G0huvj1xw@mail.gmail.com>

Am 03.11.2011 14:44, schrieb Bartosz Szatkowski:
> Hi,
> below proposed API for MAP client in obex-client, for now just some
> generic functions and browsing support.
>
> Messages Access hierarchy
> =========================
>
> Service         org.openobex.client
> Interface       org.openobex.MessagesAccess

Are there any plan on switching to a different namespace?
Using openobex was always in conflict with previously existing software 
(o-d-s) and with the switch to gobex for the client, it's even less 
correct.

HS


  reply	other threads:[~2011-11-03 13:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-03 13:44 [RFC] API for MAP client in obex-client Bartosz Szatkowski
2011-11-03 13:52 ` Hendrik Sattler [this message]
2011-11-03 14:00 ` Bartosz Szatkowski
2011-11-03 14:08 ` Hendrik Sattler
2011-11-03 14:16   ` Bartosz Szatkowski
2011-11-03 15:13     ` Luiz Augusto von Dentz
2011-11-03 15:41       ` Anders Widen
2011-11-03 17:38       ` Bartosz Szatkowski
2011-11-03 17:59         ` Luiz Augusto von Dentz
2011-11-03 19:01           ` Bartosz Szatkowski
2011-11-04 12:00             ` Luiz Augusto von Dentz
2011-11-07  9:46               ` Bartosz Szatkowski
2011-11-07 10:37                 ` Luiz Augusto von Dentz
2011-11-07 12:42                   ` Bartosz Szatkowski
2011-11-07 13:20                     ` Luiz Augusto von Dentz
2011-11-07 15:10                       ` Bartosz Szatkowski
2011-11-07 19:38                         ` 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=9a761ff17e9379d239fb223e2bc4440f@mail.hendrik-sattler.de \
    --to=post@hendrik-sattler.de \
    --cc=linux-bluetooth@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox