From: "Stotland, Inga" <inga.stotland@intel.com>
To: "michal.lowas-rzechonek@silvair.com"
<michal.lowas-rzechonek@silvair.com>,
"Gix, Brian" <brian.gix@intel.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: mesh: org.bluez.mesh.Element.MessageReceived method does not provide destination address
Date: Mon, 30 Sep 2019 16:34:24 +0000 [thread overview]
Message-ID: <f690abe8480c06b2f942465c68705b92bf4a34b4.camel@intel.com> (raw)
In-Reply-To: <20190930071803.nvp3ema26ynuiwz3@mlowasrzechonek2133>
[-- Attachment #1: Type: text/plain, Size: 1923 bytes --]
Hi Michal, Brian,
On Mon, 2019-09-30 at 09:18 +0200, michal.lowas-rzechonek@silvair.com
wrote:
> Brian, Inga,
>
> On 09/27, Gix, Brian wrote:
> > > For a single MessageReceived() method, the cleanest way is to
> > > have the
> > > subscription address parameter as a variant (suggested by Michal)
> > > or as
> > > a dictionary.
> > > An array introduces an extra consideration of byte ordering for
> > > group
> > > addresses.
> >
> > If variants are easy to sort in scripting languages like python3,
> > than I
> > suppose I could live with this.
>
> Last time I checked, it was C that had issues with any type of
> 'dynamic' typing, so I wouldn't worry about client languages.
> Handling
> D-Bus variants in python is trivial.
>
> > Or is this still a two step process of:
> > 1. Determining the u16 vs u128
> > 1.1 unmarshalling the correct type...
> >
> > What would the signature of the method look like?
>
> Something like this:
>
> void MessageReceived(uint16 source, uint16 key_index,
> variant destination,
> array{byte} data)
>
> and on the Python side, the handling would look somewhat like this
> (since Python doesn't do overloading, at all):
>
> class ElementInterface:
> def MessageReceived(source, key_index, destination, data):
> if type(destination) == dbus.types.UINT16:
> group_destination = destination
> elif type(destination) == dbus.types.ARRAY:
> virtual_destination = uuid.UUID(destination)
> else:
> raise DBusError('Unrecoenized destination type')
>
> > > What I mostly about is that the represenation of the subscription
> > > address in the MessageReceived() method corresponds to the
> > > representation in the configuration dictionaries for the Attach()
> > > and
> > > UpdateModelConfiguration() methods.
>
> Agreed.
>
I am fine with this version.
Regards,
Inga
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3265 bytes --]
next prev parent reply other threads:[~2019-09-30 16:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-30 18:43 mesh: org.bluez.mesh.Element.MessageReceived method does not provide destination address Michał Lowas-Rzechonek
2019-09-04 19:25 ` Michał Lowas-Rzechonek
2019-09-04 19:48 ` Michał Lowas-Rzechonek
2019-09-04 20:26 ` Gix, Brian
2019-09-04 22:39 ` Stotland, Inga
2019-09-05 7:29 ` michal.lowas-rzechonek
2019-09-05 7:34 ` michal.lowas-rzechonek
2019-09-18 8:52 ` Michał Lowas-Rzechonek
2019-09-18 12:36 ` Michał Lowas-Rzechonek
2019-09-25 19:02 ` Stotland, Inga
2019-09-26 15:18 ` Gix, Brian
2019-09-26 20:41 ` Stotland, Inga
2019-09-26 23:48 ` Gix, Brian
2019-09-27 2:54 ` Stotland, Inga
2019-09-27 8:52 ` michal.lowas-rzechonek
2019-09-27 15:01 ` Gix, Brian
2019-09-27 15:50 ` Gix, Brian
2019-09-27 17:25 ` Stotland, Inga
2019-09-27 19:25 ` Gix, Brian
2019-09-30 7:18 ` michal.lowas-rzechonek
2019-09-30 16:34 ` Stotland, Inga [this message]
2019-09-30 17:57 ` 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=f690abe8480c06b2f942465c68705b92bf4a34b4.camel@intel.com \
--to=inga.stotland@intel.com \
--cc=brian.gix@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=michal.lowas-rzechonek@silvair.com \
/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