Hi,
I have an another question, this patch only use a remote device
address as a identifier,
it may doesn't work well when mutli-p2p interface. maybe this question
is too
early this time, but the case about mutli-p2p interface is a reasonable.
so what I mean is that using a combination of local device address and
remote device address
as a identifier maybe have a good expansibility:dfd, just like the
wifi service identifier.
Yep good remark, this is a known issue due to the fact p2p technology
does not own any device (read first patches on src/technology.c)
I skip this for now, or then this patch-set would just blow up.
It's not only a small relationship from ident point of view, but it requires
some work to keep a proper relation with peer object and device, and all
issues about it.
(for other technology: such relationship exists through network.c, but
here we don't have it)
I will fix this in the next patch-set (connection/disconnection of a
peer) since it's more related to that:
at that point connman want to keep track which device knows what.
Here the point was just to introduce p2p technology and the really basic
scan functionality.
Tomasz
_______________________________________________
connman mailing list
[email protected]
https://lists.connman.net/mailman/listinfo/connman
