From: Johan Hedberg <johan.hedberg@gmail.com>
To: Vinicius Costa Gomes <vinicius.gomes@openbossa.org>
Cc: Mike <puffy.taco@gmail.com>,
linux-bluetooth <linux-bluetooth@vger.kernel.org>
Subject: Re: reverse SDP issue
Date: Wed, 21 Mar 2012 09:45:17 -0300 [thread overview]
Message-ID: <20120321124517.GB8888@x220> (raw)
In-Reply-To: <20120320173546.GA6307@samus>
Hi Vinicius,
On Tue, Mar 20, 2012, Vinicius Costa Gomes wrote:
> > As for the partial service removal changes to the device driver API, it
> > looks pretty messy to me. Is there any reason why we couldn't just
> > restrict calling remove() for when removing the entire device object
> > (and never call it when doing subsequent service discoveries)?
>
> I agree that the logic is quite messy. Just some comments:
>
> That assumes that the service list that a device implements is very much
> static, which only breaks for development (in which the services of an
> device are always changing) and you will need to remove that device and
> create it again.
We would still be able to handle added UUIDs just fine. The only issue
is with removed services in which case you'd just wouldn't be able to
connect to the remote device through the corresponding D-Bus interface
(something which can already now happen and which I think is ok).
Johan
next prev parent reply other threads:[~2012-03-21 12:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 22:19 reverse SDP issue Mike
2012-03-19 22:36 ` Mike
2012-03-19 23:04 ` Johan Hedberg
2012-03-20 17:35 ` Vinicius Costa Gomes
2012-03-20 18:27 ` Mike
2012-03-20 18:39 ` Mike
2012-03-20 19:21 ` Mike
2012-03-20 20:18 ` Mike
2012-03-21 12:45 ` Johan Hedberg [this message]
2012-03-21 13:11 ` Query on attribute api service object path Jaganath
2012-03-21 14:18 ` Anderson Lizardo
2012-03-21 14:27 ` Jaganath
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=20120321124517.GB8888@x220 \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=puffy.taco@gmail.com \
--cc=vinicius.gomes@openbossa.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