On 08/21/2012 11:55 PM, Daniel Veillard wrote: > On Wed, Aug 22, 2012 at 11:47:03AM +0800, Daniel Veillard wrote: >> On Tue, Aug 21, 2012 at 11:26:08PM -0400, Laine Stump wrote: >> [...] > [...] >> So that will work as long as we don't add namespace to the XML >> Another problem is making sure we have the addressing complete, >> for example suppose we have >> < > 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... That particular example could never happen, but in the general case I see what you mean. -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list