From: Johan Hedberg <johan.hedberg@nokia.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] [DBUS Patch] Device Property
Date: Fri, 18 Nov 2005 13:26:11 +0200 [thread overview]
Message-ID: <20051118112611.GA17062@localhost.localdomain> (raw)
In-Reply-To: <3013cac80511180251w1d2fa8f5s80ce1da7318327e7@mail.gmail.com>
On Fri, Nov 18, 2005, Eduardo Rocha wrote:
> Could you give any comments about the hci_send_req timeout (maybe is
> too high)
I'd guess that the command should take max. 100ms, so 2s timeout is
probably unnecessarely big. However, Marcel might have had a good reason
to use the current timeout in hciconfig.
> and the extended inquire parameters that is set cmd_name function in
> hciconfig app (is that needed here?).
If it's not there, then we should at least provide a D-BUS method to set
the extended inquiry parameters (which is probably a good thing as the
user might want to have other informantion there besides the name, e.g.
SDP UUID list).
> About the parameters, I've done an if to detect each property name so
> we can treat the parameter diferently.
Yeah, you're right, that works also. However, I was thinking of
solutions where dbus-send wouldn't need to know the property name -
property type mapping.
Johan
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&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-11-18 11:26 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
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 [this message]
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=20051118112611.GA17062@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.