A Peer object has to provide a pre-parsed description of the peer
services.
---
doc/peer-api.txt | 38 +++++++++++++++++++++++++++++++++++---
1 file changed, 35 insertions(+), 3 deletions(-)
diff --git a/doc/peer-api.txt b/doc/peer-api.txt
index 59a3351..0700e92 100644
--- a/doc/peer-api.txt
+++ b/doc/peer-api.txt
@@ -58,7 +58,39 @@ Properties string State [readonly] [experimental]
The current configured IPv4 netmask.
- array{array{byte}} Services [readonly] [experimental]
+ array{dict} Services [readonly] [experimental]
- Array of P2P service specifications, which are
- themselves a TLV formated byte array.
+ Array of P2P service specifications, which follow this
+ format:
+
+ String UpnpService [readonly]
+
+ The UPNP service URI.
+
+ int32 UpnpVersion [readonly]
+
+ The UPNP version in use.
+
+ array{byte} BonjourQuery [readonly]
+
+ The bonjour service query data, provided
+ through a byte array.
+
+ Note: a Peer object will never show this
+ information since, when scanning, a device
+ gets only the bonjour response data. This
+ information, however, is mandatory when a
+ bonjour service is given through Manager's
+ methods Un/RegisterPeerService.
+
+ array{byte} BonjourResponse [readonly]
+
+ The bonjour service response data, provided
+ through a byte array.
+
+ Note: this will be the only bonpour related
+ information a Peer object will show.
+
+ Note: such service specification comes either with a
+ UPNP service description or a bonjour service
+ description, not both.
--
1.8.5.5
_______________________________________________
connman mailing list
connman@connman.net
https://lists.connman.net/mailman/listinfo/connman
