mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-12-22 17:34:18 +03:00
5841d64d25
Admin API needs a way of addressing specific clients. Unlike servers, which we are happy to address by names both because its name reflects its purpose (to some extent) and we only have two of them (so far), naming clients doesn't make any sense, since a) each client is an anonymous, i.e. not recognized after a disconnect followed by a reconnect, b) we can't predict what kind of requests it's going to send to daemon, and c) the are loads of them comming and going, so the only viable option is to use an ID which is of a reasonably wide data type. Signed-off-by: Erik Skultety <eskultet@redhat.com> |
||
|---|---|---|
| .. | ||
| input-data-admin-nomdns.json | ||
| input-data-admin-server-names.json | ||
| input-data-anon-clients.json | ||
| input-data-client-ids.json | ||
| input-data-initial-nomdns.json | ||
| input-data-initial.json | ||
| input-data-no-keepalive-required.json | ||
| output-data-admin-nomdns.json | ||
| output-data-admin-server-names.json | ||
| output-data-anon-clients.json | ||
| output-data-client-ids.json | ||
| output-data-initial-nomdns.json | ||
| output-data-initial.json | ||
| output-data-no-keepalive-required.json | ||
| README | ||
virnetservertest data files =========================== The various input-data-*.json files are a record of all the historical formats that libvirt has been able to produce data for. Everytime a new field is added to the JSON output, a *new* input data file should be created. We must not add new fields to existing input-data files, nor must we ever re-structure them if code changes, as we must check new code handles the legacy formats. The various output-data-*.json files are the record of what the *new* JSON output should look like for the correspondingly named input-data file. It is permissible to change the existing output-data-*.json files if the format we save in is updated.