public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Luiz Augusto von Dentz" <luiz.dentz@gmail.com>
To: "Johan Hedberg" <johan.hedberg@nokia.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Adapter API - Devices property not updated if connection initiated by remote device
Date: Fri, 12 Dec 2008 22:02:46 -0300	[thread overview]
Message-ID: <2d5a2c100812121702j5db4d6b4sbdbbd2f5e0cdc0fe@mail.gmail.com> (raw)
In-Reply-To: <20081212132850.GA2126@localhost>

Hi

On Fri, Dec 12, 2008 at 10:28 AM, Johan Hedberg <johan.hedberg@nokia.com> wrote:
> There definitely needs to be a way to know that a remote device has
> connected to us even if it is not paired. I think we should just
> populate the Devices list in this case and then remove the device from
> it once it disconnects (if it didn't pair before that) and also send all
> appropriate signals while doing this. For knowing if the device is
> paired or not we already have the separate Paired property.

We could create the device object, but we should be careful to not
start a service discovery and end up with this device on the storage.
Note that this can be a security problem, since normally connections
should at least trigger authorization which requires the object
anyway, so someone is not really asking to the agent to authorize a
incoming connection.


-- 
Luiz Augusto von Dentz
Engenheiro de Computação

      reply	other threads:[~2008-12-13  1:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-11  3:57 Adapter API - Devices property not updated if connection initiated by remote device Bea Lam
2008-12-12  1:43 ` Marcel Holtmann
2008-12-12  4:52   ` Bea Lam
2008-12-12 10:58     ` Marcel Holtmann
2008-12-12 13:28       ` Johan Hedberg
2008-12-13  1:02         ` Luiz Augusto von Dentz [this message]

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=2d5a2c100812121702j5db4d6b4sbdbbd2f5e0cdc0fe@mail.gmail.com \
    --to=luiz.dentz@gmail.com \
    --cc=johan.hedberg@nokia.com \
    --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