Issues with new D-Bus API

[Marcel Holtmann]

Hi Witold,

> >>>> 3) For some reason the new debug properties don't work in d-feet.
> >>>>
> >>> Works for me. Take note that d-feet doesn't show properties which value
> >>> is zero or false. If you run wpa_supplicant with -dd option then all
> >>> debug properties are zero or false. Try using other DBus debugger like
> >>> qdbusviewer or get these properties some other way then with d-feet.
> >> You are right, d-feet is utterly stupid in this area.
> >>
> >> However we always include RSNIE, WPAIE and WPSIE all the time now. At
> >> least it seems they are in the introspection data. However the Get call
> >> then fails. Or something similar. I haven't really debugged this yet.
> > 
> > so I looked into this right now. And the introspection data contains the
> > property while we are not returning it in GetAll or in the properties
> > included in the BSSAdded signal.
> > 
> > This behavior is fully consistent to what we had before. I prefer it
> > this way, but this means we have to NOT include these properties in the
> > introspection data.
> 
> We can't have some properties of the interface exposed in one object and
> not exposed in another. Interface should be well defined and shouldn't
> change between objects.

not sure if that is a really strict rule in D-Bus, because you do have
essentially introspection. However I am okay with exposing empty IE
properties.

> There was a bug in IEs getters which caused to return empty message when
> no IE was present, and so there was no those properties in GetAll dict.
> It's fixed now (in my git), so the getters return an empty array if no
> IE is present in BSS.

Great.

Regards

Marcel