<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Apr 9, 2017 at 1:27 PM, Fabrice Bacchella <span dir="ltr"><<a href="mailto:fabrice.bacchella@orange.fr" target="_blank">fabrice.bacchella@orange.fr</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-"><br>
> Le 9 avr. 2017 à 11:25, Yaniv Kaul <<a href="mailto:ykaul@redhat.com">ykaul@redhat.com</a>> a écrit :<br>
><br>
<br>
> However, I tend to agree with closing the bug - I'd create a library (module) *on top of the SDK* . The comment in the bug is quite clear about it:<br>
> "The objective of the SDK is to offer the same that the API offers, without the burden of the details of the HTTP and XML handling. Nothing less, and nothing more."<br>
<br>
</span>Then don't call it a SDK, they are barely helper functions with bad design decisions, connection.vms_service().vm_<wbr>service(id) is nothing else than redundancy and bring nothing else than noise.<br></blockquote><div><br></div><div><a href="http://www.ovirt.org/community/about/community-guidelines/#be-respectful">http://www.ovirt.org/community/about/community-guidelines/#be-respectful</a></div><div><br></div><div>Y.</div><div> </div></div><br></div></div>