Re: [libvirt] RFC: take two on live update of network configuration

On Wed, Aug 22, 2012 at 11:47:03AM +0800, Daniel Veillard wrote: [...] Oops i didn't finish that argument supose we have somewhere <foo> ... </foo> <foo> ... </foo> first are the element always sorted in a coherent fashion internally so that if we do //foo[2] we know which one is pointed at, or if we can guarantee order can we guarantee that for all constructs there is an identifier like an attribute allowing unique selection (like availability of an ip address) My concern is an API with hole, where there is no way to guarantee reaching the element we want to modify, and risking touching something else. Say for example 2 interface with DHCP and no IP... Daniel -- Daniel Veillard | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ daniel(a)veillard.com | Rpmfind RPM search engine http://rpmfind.net/ http://veillard.com/ | virtualization library http://libvirt.org/