From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Patch: GetRemoteClass
Date: Wed, 02 Aug 2006 05:13:26 +0200 [thread overview]
Message-ID: <1154488406.3905.37.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <200608011329.03106.denis.kenzior@trolltech.com>
Hi Denis,
> Attached is a patch to get remote class of device information as a uint32.
> This introduces a new method with signature:
> uint32 GetRemoteClass(string address), which returns the class of device
> information encoded as a 32 bit integer.
>
> The reasoning is that some applications might want to rely on their own
> conversion routines for the Major, Minor and Service class attributes, and
> thus the DBUS GetRemoteMajorClass, GetRemoteMinorClass, etc methods that
> return strings are not useful.
the patch is clean. So before I apply it and so extend the API, does
someone else thinks it is useful to have?
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-08-02 3:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-01 3:29 [Bluez-devel] Patch: GetRemoteClass Denis KENZIOR
2006-08-02 3:13 ` Marcel Holtmann [this message]
2006-08-02 11:04 ` Peter Wippich
2006-08-09 22:09 ` 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=1154488406.3905.37.camel@aeonflux.holtmann.net \
--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