On Tue, Jan 10, 2012 at 10:13:59AM -0700, Eric Blake wrote: > On 01/10/2012 09:55 AM, Daniel P. Berrange wrote: > > These 2 things feel like overloading the API with two different > > semantics. On the one hand I see a simple XML -> struct -> XML > > transformation, which is driver indepedant and does not need to > > get any HV state. I call this canonicalization > > We still want it to be connection-dependent, though, so that the > canonicalization is tied to the version of the driver the user is > connected to, and not to the version of the libvirt.so client, in the > case where the driver and client are at different versions. Oh sure, still needs to run server side - we can have 1 shared impl that can be pulled in by all drivers - as we do for nodeinfo stuff that's shared. 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