From: Johan Hedberg <johan.hedberg@nokia.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Remote name delay
Date: Wed, 14 Dec 2005 23:53:44 +0200 [thread overview]
Message-ID: <20051214215318.GA25332@localhost.localdomain> (raw)
In-Reply-To: <e1effdeb0512141035w5cc40fach9d77ead5df00cf2@mail.gmail.com>
Hi Claudio,
On Wed, Dec 14, 2005, Claudio Takahasi wrote:
> ok. We will extend the GetProperty(string:info) returning the
> following arguments:
> - MAC Address: String
> - Device Status: String(UP/DOWN)
> - Manufacturer: String
> - HCI Version: String
> - HCI Revision: String
> - LMP Version: String
> - LMP Sub Version: String
Currently we have three different property types: string, boolean and
byte. Are you proposing that the above information be bundled to one
"info" property? That would create a fourth property type which, in my
opinion, would complicate the code unecessarely. Maybe those pieces of
information should be split into one property each (or maybe that's what
you're suggesting, sorry if I misunderstood)? If there still exists a
complelling reason to bundle all that info into one property, then I'd
suggest creating a new property with the type DBUS_TYPE_STRUCT in order
to maintain consistency with the parameters of the property signal and
methods.
Also, all of the above pieces of information, excluding the device
status, are of a read-only nature so the SetProperty method and
PropertyChanged signal don't really apply to them. Therefore the
question should be asked whether the "properties" feature is the right
one to use for them (I'm not saying it isn't, just that it should be
questioned). E.g. you would need to think about what error should be
returned if SetProperty is called for one of them.
Thirdly, the device status information can already changed using the Up
and Down methods and its changes can be tracked using the Up and Down
signals, so adding it to the set of properties is probably not the right
thing to do (or then the Up/Down signals and methods should be removed).
Johan
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-12-14 21:53 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 [this message]
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
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=20051214215318.GA25332@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.