Daniel P. Berrange c1b412f1d9 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>		2017-01-23 15:32:46 +00:00
..
channel-buffer.h	Clean up ill-advised or unusual header guards	2016-07-12 16:20:46 +02:00
channel-command.h	Clean up ill-advised or unusual header guards	2016-07-12 16:20:46 +02:00
channel-file.h	Clean up ill-advised or unusual header guards	2016-07-12 16:20:46 +02:00
channel-socket.h	Clean up ill-advised or unusual header guards	2016-07-12 16:20:46 +02:00
channel-tls.h	Clean up ill-advised or unusual header guards	2016-07-12 16:20:46 +02:00
channel-util.h	Clean up ill-advised or unusual header guards	2016-07-12 16:20:46 +02:00
channel-watch.h	Clean up ill-advised or unusual header guards	2016-07-12 16:20:46 +02:00
channel-websock.h	Clean up ill-advised or unusual header guards	2016-07-12 16:20:46 +02:00
channel.h	io: add ability to set a name for IO channels	2016-10-27 09:13:10 +02:00
dns-resolver.h	io: introduce a DNS resolver API	2017-01-23 15:32:46 +00:00
task.h	io: remove Error parameter from QIOTask thread worker	2017-01-23 15:32:19 +00:00