From: Johan Hedberg <johan.hedberg@gmail.com>
To: Luiz Von Dentz <luiz.dentz@gmail.com>
Cc: "Stotland, Inga" <inga.stotland@intel.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
Marcel Holtmann <marcel@holtmann.org>,
"Gix, Brian" <brian.gix@intel.com>
Subject: Re: [PATCH BlueZ v2] doc: Initial Bluetooth Mesh API
Date: Mon, 12 Nov 2018 13:58:07 +0100 [thread overview]
Message-ID: <4C0377DF-430B-4A2C-BA6E-CC4B9C6ED9F6@gmail.com> (raw)
In-Reply-To: <CABBYNZJLLxNC3BQvyDxzTFLppe25ke=VK_9QtvJsNbCFjnUW2A@mail.gmail.com>
Hi Luiz
> On 12 Nov 2018, at 13.24, Luiz Augusto von Dentz <luiz.dentz@gmail.com> wrote:
>
> It seems wrong to me to have to send your own object as method
> argument, usually this sort of communication goes as a Signal but it
> seems the Element interface has no signal to be able to do something
> like that.
The problem with signals is that they cannot return an error, and I do think we’d want to have the daemon return an error if it cannot send the given message. Also, by default signals are broadcast, and it feels a bit hawkish to do unicast destinations for them.
Johan
next prev parent reply other threads:[~2018-11-12 12:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 1:33 [PATCH BlueZ v2] doc: Initial Bluetooth Mesh API Inga Stotland
2018-11-12 12:24 ` Luiz Augusto von Dentz
2018-11-12 12:58 ` Johan Hedberg [this message]
2018-11-12 14:40 ` Luiz Augusto von Dentz
2018-11-12 16:05 ` Gix, Brian
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=4C0377DF-430B-4A2C-BA6E-CC4B9C6ED9F6@gmail.com \
--to=johan.hedberg@gmail.com \
--cc=brian.gix@intel.com \
--cc=inga.stotland@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
/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).