public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Bea Lam <blam@trolltech.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 11:58:47 +0100	[thread overview]
Message-ID: <1229079527.22285.38.camel@violet.holtmann.net> (raw)
In-Reply-To: <200812121452.37564.blam@trolltech.com>

Hi Bea,

can you please stop top-posting. Like every other open source mailing
list we are using bottom-posting and you are just destroying the flow of
the replies with top-posting. And KMail is perfectly capable of doing
so ;)

> Yes, FindDevice() is useful when I need to check whether a particular device 
> is connected at the moment. But what if I don't know the address of the 
> connecting device? That is, should BlueZ also be able to tell me when some 
> random, unknown device connects to me?

I think we do create a temporary device structure for incoming
connections in all cases since that is needed for pairing. However we
might not add this to the Devices list.

Johan, any comments here. Should we just send out signals? I think the
current reason for not doing so is that in most cases this is during a
pairing event and we do wanna wait until it succeeds. However I don't
see the big harm in adding it to the list.

Regards

Marcel



  reply	other threads:[~2008-12-12 10:58 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 [this message]
2008-12-12 13:28       ` Johan Hedberg
2008-12-13  1:02         ` 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=1229079527.22285.38.camel@violet.holtmann.net \
    --to=marcel@holtmann.org \
    --cc=blam@trolltech.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