From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] The new D-Bus API specification
Date: Fri, 03 Mar 2006 14:55:58 +0100 [thread overview]
Message-ID: <1141394159.4814.3.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <e1effdeb0603021302h2ffbcd80y1a9c46bf93e51278@mail.gmail.com>
Hi Claudio,
> I tested the latest bluez-utils CVS version with the recent D-Bus
> changes and I have some comments:
>
> * Policy
> I'm not sure, but I think some linux distributions use pam_console
> instead of at_console. We sould investigate more to avoid future
> problems. Another thing are the rules. at_console aims provide a way
> to refer to users that are not physically sitting in front of the
> computer. I tested send D-Bus messages from the local host or
> connected through ssh and I didn't noticed differences. I mean, the
> behaviour is the same. Remote users still able to send D-Bus messages.
actually the at_console should be transparent between different Linux
distributions. However we need to verify that it works on at least
Fedora, SuSE, Debian and Ubuntu.
> * Device->Adapter
> Maybe should be better if we rename the function names and constants
> too. Or remove the prefix "dev" and "DEV". These prefixes were added
> to avoid confusion when all functions were in the same file.
Remove the prefix completely, because it is all internal.
> * Error
> I noticed that there are different handling of hci_open_dev result.
> I found bluez_new_failure_msg and error_no_such_device calls to handle
> the same error. I will send a patch to use the same approach.
Go ahead and send fixed. I am to busy to fully complete that change.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&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-03-03 13:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 23:58 [Bluez-devel] The new D-Bus API specification Marcel Holtmann
2006-02-24 19:05 ` Marcel Holtmann
2006-03-02 21:02 ` Claudio Takahasi
2006-03-03 13:55 ` Marcel Holtmann [this message]
2006-03-04 20:15 ` Sjoerd Simons
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=1141394159.4814.3.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;
as well as URLs for NNTP newsgroup(s).