From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] [DBUS PATCH] GetAlias crash
Date: Thu, 23 Feb 2006 00:45:32 +0100 [thread overview]
Message-ID: <1140651932.4519.57.camel@localhost> (raw)
In-Reply-To: <1140644211.4519.49.camel@localhost>
Hi Claudio,
> > Now, the daemon is returning the same error message used in the
> > RemoteAlias: "Error org.bluez.Error: No such device or address".
> > Is it ok?
>
> The GetAlias and RemoteAlias must become GetRemoteAlias. I spent some
> time thinking about it and after writing the first code for it, I
> actually realized that GetRemoteAlias and SetRemoteAlias methods and
> RemoteAliasChanged signal would be much better and cleaner.
I did all the needed changes and finally checked in a first draft
version of the D-Bus API document.
We now really need the dbus-test script working with the new API and I
think we also should write a bunch of regression tests for testing our
new API.
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-02-22 23:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 19:42 [Bluez-devel] [DBUS PATCH] GetAlias crash Claudio Takahasi
2006-02-22 21:36 ` Marcel Holtmann
2006-02-22 23:45 ` Marcel Holtmann [this message]
2006-02-23 11:51 ` Claudio Takahasi
2006-02-23 12: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=1140651932.4519.57.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;
as well as URLs for NNTP newsgroup(s).