<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div apple-content-edited="true">
<div><br></div></div><div><div>On 17 Jan 2014, at 22:06, Robert Collins <<a href="mailto:robertc@robertcollins.net">robertc@robertcollins.net</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">On 17 January 2014 09:22, Renat Akhmerov <<a href="mailto:rakhmerov@mirantis.com">rakhmerov@mirantis.com</a>> wrote:<br><blockquote type="cite">Since it’s pretty easy to get lost among all the opinions I’d like to<br>clarify/ask a couple of things:<br><br>Keeping all the clients physically separate/combining them in to a single<br>library. Two things here:<br><br>In case of combining them, what exact project are we considering? If this<br>list is limited to core projects like nova and keystone what policy could we<br>have for other projects to join this list? (Incubation, graduation,<br>something else?)<br>In terms of granularity and easiness of development I’m for keeping them<br>separate but have them use the same boilerplate code, basically we need a<br>OpenStack Rest Client Framework which is flexible enough to address all the<br>needs in an abstract domain agnostic manner. I would assume that combining<br>them would be an additional organizational burden that every stakeholder<br>would have to deal with.<br><br>Has anyone ever considered an idea of generating a fully functional REST<br>client automatically based on an API specification (WADL could be used for<br>that)? Not sure how convenient it would be, it really depends on a<br>particular implementation, but as an idea it could be at least thought of.<br>Sounds a little bit crazy though, I recognize it :).<br></blockquote><br>Launchpadlib which builds on wadllib did *exactly* that. It worked<br>fairly well with the one caveat that it fell into the ORM trap - just<br>in time lookups for everything with crippling roundtrips.<br><br></div></blockquote><br></div><div>Thanks, I’ll have a look at it.</div><br><div><br></div></body></html>