summaryrefslogtreecommitdiff
path: root/io/Makefile.objs
diff options
context:
space:
mode:
authorDaniel P. Berrange <berrange@redhat.com>2016-07-19 12:54:47 +0100
committerDaniel P. Berrange <berrange@redhat.com>2017-01-23 15:32:46 +0000
commitc1b412f1d94ba717896f876dbf59fffa91e596fc (patch)
tree74603d5bd4f1bbe41cd974d22b79c6bba377604b /io/Makefile.objs
parent59de517d8d482416a079da7ee8344187d513d4a4 (diff)
downloadqemu-c1b412f1d94ba717896f876dbf59fffa91e596fc.tar.gz
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>
Diffstat (limited to 'io/Makefile.objs')
-rw-r--r--io/Makefile.objs1
1 files changed, 1 insertions, 0 deletions
diff --git a/io/Makefile.objs b/io/Makefile.objs
index 9d8337d89a..12983cca79 100644
--- a/io/Makefile.objs
+++ b/io/Makefile.objs
@@ -7,4 +7,5 @@ io-obj-y += channel-tls.o
io-obj-y += channel-watch.o
io-obj-y += channel-websock.o
io-obj-y += channel-util.o
+io-obj-y += dns-resolver.o
io-obj-y += task.o