From: Phil Blundell <pb@nexus.co.uk>
To: Fred Sch??ttgen <bluez-devel@schaettgen.de>
Cc: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] D-Bus interfaces
Date: Mon, 16 Feb 2004 14:46:15 +0000 [thread overview]
Message-ID: <20040216144615.GA318@nexus.co.uk> (raw)
In-Reply-To: <200402090015.24318.bluez-devel@schaettgen.de>
on Mon, Feb 09, 2004 at 12:15:24AM +0100, Fred Sch??ttgen wrote:
> On Sunday 08 February 2004 23:31, Marcel Holtmann wrote:
> > Do we need a special datatype for the BD_ADDR or is string the best?
>
> I can only speak from my experience with dcop, but I would try to use standard
> types whereever it's possible. In case that there exists a d-bus counterpart
> to the dcop command line utility (dbus-send maybe?), it would make the bluez
> interface more accessible for scripts.
Yes, agreed. In my experiments with D-BUS and BlueZ so far, I've been
using a simple byte array for the address. Encoding it as an ASCII
string would be another possibility, but this would generally make the
marshalling/unmarshalling process more expensive, and doesn't really
gain you anything.
p.
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&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:[~2004-02-16 14:46 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-08 18:35 [Bluez-devel] D-Bus support Marcel Holtmann
2004-02-08 18:51 ` Fredrik Noring
2004-02-08 19:09 ` Marcel Holtmann
2004-02-08 21:07 ` Fredrik Noring
2004-02-08 22:04 ` Marcel Holtmann
2004-02-08 22:33 ` Fredrik Noring
2004-02-08 21:28 ` [Bluez-devel] D-Bus interfaces Fredrik Noring
2004-02-08 21:54 ` Marcel Holtmann
2004-02-08 22:15 ` Fredrik Noring
2004-02-08 22:31 ` Marcel Holtmann
2004-02-08 22:50 ` Fredrik Noring
2004-02-08 23:19 ` Marcel Holtmann
2004-02-08 23:51 ` Fredrik Noring
2004-02-09 0:38 ` Marcel Holtmann
2004-02-09 7:22 ` Fredrik Noring
2004-02-09 10:06 ` Marcel Holtmann
2004-02-09 10:22 ` Fredrik Noring
2004-02-09 10:38 ` Marcel Holtmann
2004-02-09 10:46 ` Fredrik Noring
2004-02-09 11:03 ` Marcel Holtmann
2004-02-09 11:53 ` Fredrik Noring
2004-02-09 13:01 ` Marcel Holtmann
2004-02-09 13:23 ` Fredrik Noring
2004-02-09 15:46 ` Marcel Holtmann
2004-02-09 16:05 ` Fredrik Noring
2004-02-09 16:30 ` Marcel Holtmann
2004-02-09 17:04 ` Fredrik Noring
2004-02-11 10:03 ` Fredrik Noring
2004-02-11 13:32 ` Marcel Holtmann
2004-02-11 14:05 ` Fredrik Noring
2004-02-11 16:45 ` Marcel Holtmann
2004-02-11 22:00 ` Fredrik Noring
2004-02-11 22:29 ` Marcel Holtmann
2004-02-11 22:33 ` Fredrik Noring
2004-02-11 12:32 ` Fredrik Noring
2004-02-11 13:28 ` Marcel Holtmann
2004-02-11 14:35 ` Fredrik Noring
2004-02-11 17:05 ` Marcel Holtmann
2004-02-11 22:25 ` Fredrik Noring
2004-02-11 22:42 ` Marcel Holtmann
2004-02-11 22:57 ` Fredrik Noring
2004-02-11 23:14 ` Marcel Holtmann
2004-02-11 23:29 ` Fredrik Noring
2004-02-11 23:36 ` Marcel Holtmann
2004-02-11 23:41 ` Fredrik Noring
2004-02-11 23:46 ` Marcel Holtmann
2004-02-08 23:15 ` Fred Schättgen
2004-02-16 14:46 ` Phil Blundell [this message]
2004-02-16 15:36 ` Marcel Holtmann
2004-02-16 15:41 ` Phil Blundell
2004-02-17 22:59 ` Marcel Holtmann
2004-02-17 23:38 ` Philip Blundell
2004-02-17 23:44 ` Marcel Holtmann
2004-02-17 23:49 ` Philip Blundell
2004-02-17 23:57 ` Marcel Holtmann
2004-02-18 0:08 ` Philip Blundell
2004-02-18 0:17 ` Marcel Holtmann
2004-02-18 0:29 ` Philip Blundell
2004-02-19 15:55 ` Fredrik Noring
2004-02-19 16:01 ` Fredrik Noring
2004-02-19 15:52 ` Fredrik Noring
2004-02-19 16:48 ` Phil Blundell
2004-02-20 4:04 ` Fredrik Noring
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=20040216144615.GA318@nexus.co.uk \
--to=pb@nexus.co.uk \
--cc=bluez-devel@lists.sourceforge.net \
--cc=bluez-devel@schaettgen.de \
/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.