From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Dbus and RemoteDeviceFound API
Date: Wed, 17 May 2006 18:03:04 +0200 [thread overview]
Message-ID: <1147881784.14106.26.camel@localhost> (raw)
In-Reply-To: <7A6DA545D7FDCC4B93DB651FDBC1EDDE46C720@eumonex01.palmsource.com>
Hi Renaud,
> I just discover that new API, and I have a remark.
>
> Is it to possible to add to that message the class of device (as an
> uint32) ?
> With this we can have complete information about discovered device even
> if major or minor are not in "constant definition" of dbus API.
> This can also simplify programation in C (ie: filtering, displaying
> icons,...)
we did it this way on purpose. If definitions are missing, then this is
a bug and needs to be fixed. What types are you missing?
Another basic design idea behind the D-Bus API for BlueZ is not to use
weird integer constants at all. We have clear text attributes which make
it very easy to use them from scripting languages like Python. However
this makes it harder for application written in C, but we accepted this
disadvantage.
Regards
Marcel
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-05-17 16:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-17 15:51 [Bluez-devel] Dbus and RemoteDeviceFound API Renaud Malaval
2006-05-17 16:03 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-17 16:44 Renaud Malaval
2006-05-17 16:54 ` Marcel Holtmann
2006-05-30 15:20 ` Frederic Danis
2006-05-30 15:34 ` 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=1147881784.14106.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