On Mon, May 09, 2016 at 09:30:30 -0400, Cole Robinson wrote:
On 05/09/2016 07:30 AM, Pavel Hrdina wrote:
On Sun, May 08, 2016 at 01:49:06PM -0400, Cole Robinson wrote:
Really wish someone would have chimed in with this to my (unresponded) RFC email about these things...
http://www.redhat.com/archives/libvir-list/2016-April/msg01839.html
That pattern is fine in this case, but what about the case of ports= element that is only supported with a controller type=usb model=nec-xhci ? Do we have new XML like:
<controller supported='yes'> <type name='usb'> <model name='nec-xhci'/> <param name='ports' supported='yes'/> </model> </type> </controller>
It seems like these types of relationships could grow deeply nested, so I opted for following the limited existing convention of adding unique enum names to represent the relationship.
Neither of those is really human friendly, thus I prefer aggregating the information to avoid having to collate them from snippets out of place.