linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Remote name delay
Date: Thu, 15 Dec 2005 20:47:15 +0100	[thread overview]
Message-ID: <1134676035.12505.26.camel@localhost> (raw)
In-Reply-To: <e1effdeb0512150817w6fc28193xe6a09d28cf1cab7a@mail.gmail.com>

Hi Claudio,

> After your feedbacks, I think it's better remove the
> "GetProperty('info')" in order to avoid confusion. We can create a new
> method called "Info(void)" to retrieve read-only properties returning:
> Address: String
> Manufacturer: String
> HCI Version: String, format TBD
> LMP Version: String, format TBD
> 
> We don't need a fild to retrieve the device status. The device
> status(UP/DOWN) signal can be tracked all the time. Keep in mind that,
> for multiple adapter scenarios will be more difficult  track the
> UP/DOWN signals. Currently, it's possible recover the device status
> using the DevList, but it's little bit expensive request/parsing all
> arguments. When the adapter is DOWN, change the adapter property will
> fail(Probably due a operation timeout), for this case get the device
> status is useful. These are the reasons why I would like receive the
> status in the "Info(void)" reply message.
> 
> The final decision is yours! :) If we consider it necessary we can add
> it in the future without problems.

at the moment I don't have any favor in any direction. Implement one and
then we see how it goes.

> For Read/Write properties:
> - auth
> - connectable
> - discoverable
> - encrypt
> - name
> - inqmode

Remove "auth" and "encrypt" from this list. I am not going to support
Security Mode 3 settings over D-Bus. They are crap anyway and hopefully
at somepoint I can convince everybody that Security Mode 3 alone makes
no sense at all.

I also don't see any need for the inquiry mode setting. Since it is all
transparent, the hcid should simply set the highest available inquiry
mode on startup and then send inquiry result signals as usual.

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      parent reply	other threads:[~2005-12-15 19:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-01 19:17 [Bluez-devel] Remote name delay Claudio Takahasi
2005-12-01 20:59 ` Marcel Holtmann
2005-12-02 11:21   ` Claudio Takahasi
2005-12-02 11:30     ` Marcel Holtmann
2005-12-02 16:33       ` Claudio Takahasi
2005-12-02 16:41         ` Bastien Nocera
2005-12-02 18:38           ` Marcel Holtmann
2005-12-13 21:52             ` Claudio Takahasi
2005-12-02 18:36         ` Marcel Holtmann
2005-12-13 21:59           ` Claudio Takahasi
2005-12-13 22:05             ` Marcel Holtmann
2005-12-14 18:35               ` Claudio Takahasi
2005-12-14 19:15                 ` Marcel Holtmann
2005-12-14 19:30                   ` Claudio Takahasi
2005-12-14 21:53                 ` Johan Hedberg
2005-12-15  5:25                   ` Marcel Holtmann
2005-12-15 16:17                     ` Claudio Takahasi
2005-12-15 16:33                       ` Johan Hedberg
2005-12-15 19:47                       ` Marcel Holtmann [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=1134676035.12505.26.camel@localhost \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).