The specification of the peer service needs to follow what's documented
in peer API.
---
doc/manager-api.txt | 18 +++++++++++-------
1 file changed, 11 insertions(+), 7 deletions(-)
diff --git a/doc/manager-api.txt b/doc/manager-api.txt
index a2ebea0..8bf31ad 100644
--- a/doc/manager-api.txt
+++ b/doc/manager-api.txt
@@ -156,20 +156,22 @@ Methods dict GetProperties()
Possible Errors: [service].Error.InvalidArguments
- void RegisterPeerService(array{byte} specification, boolean
master) [experimental]
+ void RegisterPeerService(dict specification, boolean master)
[experimental]
Registers a local P2P Peer service
- If p2p technology is not available, this will raise a
- 'not supported' error. This behavior does not apply if
- such technology is just disabled.
+ Even if p2p techonology is not available, it will be
+ possible to register peer services, since a p2p
+ enabled device might appear at anytime. ConnMan will
+ then ensure to properly register those services to the
+ p2p device.
A Peer service belongs to the process that registers
it, thus if that process dies, its Peer services will
be destroyed as well.
- "specification" is the TLV formated byte array
- describing the WiFi P2P service.
+ "specification" is a dict following the format
+ described in Peer API document.
ConnMan will be able to determine in most cases
whether to be the P2P Group Owner or not. If the
@@ -179,13 +181,15 @@ Methods dict GetProperties()
you know what you are doing.
Possible Errors: [service].Error.InvalidArguments
+ [service].Error.AlreadyExists
[service].Error.NotSupported
- void UnregisterPeerService(array{byte} specification)
[experimental]
+ void UnregisterPeerService(dict specification) [experimental]
Unregisters an existing local P2P Peer service
Possible Errors: [service].Error.InvalidArguments
+ [service].Error.NotRegistered
Signals TechnologyAdded(object path, dict properties)
--
1.8.5.5
_______________________________________________
connman mailing list
[email protected]
https://lists.connman.net/mailman/listinfo/connman