From: Johan Hedberg <johan.hedberg@nokia.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] [DBUS Patch] Device Property
Date: Wed, 9 Nov 2005 00:20:33 +0200 [thread overview]
Message-ID: <20051108222033.GA12368@localhost.localdomain> (raw)
In-Reply-To: <e1effdeb0511081241w20503576id78ab38764b8b96b@mail.gmail.com>
On Tue, Nov 08, 2005, Claudio Takahasi wrote:
> In my opinion we can start playing with the feature below:
>
> up Open and initialize HCI device
> down Close HCI device
These we already have (through the Up and Down methods).
> name [name] Get/Set local name
This is good to have. A "local name changed" signal might also be useful
so that other applications can update their UI. Actually now that I
think about it, maybe thare should be a generic "property changed"
signal for all properties.
> auth Enable/Disable Authentication
> encrypt Enable/Disable Encryption
> secmgr Enable/Disable Security Manager
> piscan Enable/Disable Page and Inquiry scan
> iscan Enable/Disable Inquiry scan
> pscan Enable/Disable Page scan
I think the piscan can be dropped so that we have two boolean
properties: iscan and pscan.
Also, I think it would be good to have the possibility to set the
inquiry mode (standard, with RSSI, RSSI + extended inq. result).
Currently the mode is always set inquiry with rssi when PeriodicInquiry
is called (I'm thinking of sending a patch to remove it), but it should
probably be set once at device initialization and then changed only by
the SetProperty method call.
Johan
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-11-08 22:20 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 14:03 [Bluez-devel] [DBUS Patch] Device Property Eduardo Rocha
2005-11-04 15:44 ` Marcel Holtmann
2005-11-08 20:41 ` Claudio Takahasi
2005-11-08 22:20 ` Marcel Holtmann
2005-11-08 22:20 ` Johan Hedberg [this message]
2005-11-08 22:38 ` Marcel Holtmann
2005-11-17 19:16 ` Eduardo Rocha
2005-11-17 20:52 ` Eduardo Rocha
2005-11-18 8:28 ` Johan Hedberg
2005-11-18 10:51 ` Eduardo Rocha
2005-11-18 11:26 ` Johan Hedberg
2005-11-18 13:00 ` Eduardo Rocha
2005-11-22 11:51 ` Marcel Holtmann
2005-11-22 19:52 ` Eduardo Rocha
2005-11-24 4:17 ` Marcel Holtmann
2005-11-24 18:50 ` Eduardo Rocha
2005-11-24 22:54 ` Marcel Holtmann
2005-11-25 13:47 ` Claudio Takahasi
2005-11-25 14:32 ` Eduardo Rocha
2005-11-25 18:08 ` Marcel Holtmann
2005-11-25 18:34 ` Eduardo Rocha
2005-11-25 18:41 ` Marcel Holtmann
2005-11-25 19:52 ` Claudio Takahasi
2005-11-25 20:06 ` Marcel Holtmann
2005-12-01 16:55 ` Eduardo Rocha
2005-12-01 21:05 ` Marcel Holtmann
2005-12-07 12:29 ` Eduardo Rocha
2005-12-07 12:55 ` Johan Hedberg
2005-12-07 13:02 ` Marcel Holtmann
2005-12-07 16:01 ` Eduardo Rocha
2005-12-13 17:27 ` Eduardo Rocha
2005-12-13 22:03 ` Marcel Holtmann
2005-12-14 19:02 ` Eduardo Rocha
2005-12-16 18:37 ` Eduardo Rocha
2005-12-16 18:40 ` Marcel Holtmann
2005-11-25 16:51 ` Johan Hedberg
2005-11-25 18:12 ` Marcel Holtmann
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=20051108222033.GA12368@localhost.localdomain \
--to=johan.hedberg@nokia.com \
--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).