mgmt1: add mgmt.label.Index and events clarification

This commit is contained in:
Marek Marczykowski-Górecki 2017-04-15 13:59:22 +02:00
parent 8f53500944
commit 9b3b0ffd04
No known key found for this signature in database
GPG Key ID: F32894BE9684938A

View File

@ -27,6 +27,7 @@ to set the policy using current mechanism.
| `mgmt.label.List` | `dom0` | - | - | `<property>\n` |
| `mgmt.label.Create` | `dom0` | label | `0xRRGGBB` | - |
| `mgmt.label.Get` | `dom0` | label | - | `0xRRGGBB` |
| `mgmt.label.Index` | `dom0` | label | - | `<label-index>` |
| `mgmt.label.Remove` | `dom0` | label | - | - |
| `mgmt.property.List` | `dom0` | - | - | `<property>\n` |
| `mgmt.property.Get` | `dom0` | property | - | `default={yes|no} type={str|int|bool|vm|label} <value>` |
@ -126,6 +127,10 @@ will not close the connection.
A method yielding events will not ever return a `OK` or `EXCEPTION` message.
When calling such method, it will produce an artificial event
`connection-established` just after connection, to help avoiding race
conditions during event handler registration.
### EXCEPTION (2)
```