| commit | c1b412f1d94ba717896f876dbf59fffa91e596fc | |
| author | Daniel P. Berrange <berrange@redhat.com> | |
| Tue, 19 Jul 2016 11:54:47 +0000 (19 12:54 +0100) | ||
| committer | Daniel P. Berrange <berrange@redhat.com> | |
| Mon, 23 Jan 2017 15:32:46 +0000 (23 15:32 +0000) | ||
| tree | 74603d5bd4f1bbe41cd974d22b79c6bba377604b | treesnapshot (tar.gz zip) |
| parent | 59de517d8d482416a079da7ee8344187d513d4a4 | commitdiff |
io: introduce a DNS resolver API
Currently DNS resolution is done automatically as part
of the creation of a QIOChannelSocket object instance.
This works ok for network clients where you just end
up a single network socket, but for servers, the results
of DNS resolution may require creation of multiple
sockets.
Introducing a DNS resolver API allows DNS resolution
to be separated from the socket object creation. This
will make it practical to create multiple QIOChannelSocket
instances for servers.
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Currently DNS resolution is done automatically as part
of the creation of a QIOChannelSocket object instance.
This works ok for network clients where you just end
up a single network socket, but for servers, the results
of DNS resolution may require creation of multiple
sockets.
Introducing a DNS resolver API allows DNS resolution
to be separated from the socket object creation. This
will make it practical to create multiple QIOChannelSocket
instances for servers.
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
| include/io/dns-resolver.h | [new file with mode: 0644] | blob |
| include/qemu/sockets.h | diffblobblamehistory | |
| io/Makefile.objs | diffblobblamehistory | |
| io/dns-resolver.c | [new file with mode: 0644] | blob |
| util/qemu-sockets.c | diffblobblamehistory |