[PATCH 5/7] dbus: Remove GroupMember object type and use Peer instead

Tomasz Bursztyka tomasz.bursztyka
Mon May 26 01:21:07 PDT 2014

Hi Jouni,

> Could you please clarify why GroupMember is unusable? Is it clear that
> there cannot be existing users of this? Please also confirm that the new
> design supports the case where multiple groups include the same devices.

In the first version of this patchset I said:

"The 5 next ones are solving 1 big issue: once we pair with another peer,
there is no proper way to find out to which group this peer now ends up 

There was some attempt to solve this via the GroupMember object, used in
Members property of a group. But - when this was used only when the group
is the GO - the GroupMember object still could not help to make any 
with the originated Peer object since it provides no properties or methods.
Not to say it was then useless in case the group is just the client."

Thus my attempt to fix this as providing peer object path in the Members 
+ the Group property in Peer object side (which is currently not 
multigroup enabled
as you noticed)


More information about the Hostap mailing list