On Wed, Feb 17, 2016 at 03:14:53PM +0300, Nikolay Shirokovskiy wrote: > Currently close callback API can only inform us of closing the connection > between remote driver and daemon. But what if a driver running in the > daemon itself can have another persistent connection? In this case > we want to be informed of that connection changes state too. > > This patch series extends meaning of current close callback API so > that now it notifies of closing of any internal persistent connection. > The overall approach is to move close callback support to drivers. This looks fine now to me. It can be pushed after the release freeze is over Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list