<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><div>On 16 Jan 2014, at 12:36, Dean Troyer <<a href="mailto:dtroyer@gmail.com">dtroyer@gmail.com</a>> wrote:</div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>I've already written a POC for solum and some other things to demonstrate how to add additional projects simply by installing the python-*client package. <a href="https://github.com/dtroyer/python-oscplugin">https://github.com/dtroyer/python-oscplugin</a> is a trivial example.</div></div></div></div></blockquote><div><br></div>Thanks, this link is helpful.<br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word"><ul><ul><li>In terms of granularity and easiness of development I’m for keeping them separate but have them use the same boilerplate code, basically we need a OpenStack Rest Client Framework which is flexible enough to address all the needs in an abstract domain agnostic manner. I would assume that combining them would be an additional organizational burden that every stakeholder would have to deal with.</li>
</ul></ul></div></blockquote><div>If it is not a library that is actually shared you will get back to the current situation over time. </div></div></div></div></blockquote><div><br></div>How is that different from any other oslo stuff?<br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div style="word-wrap:break-word"><div><ul><li>Has anyone ever considered an idea of generating a fully functional REST client automatically based on an API specification (WADL could be used for that)? Not sure how convenient it would be, it really depends on a particular implementation, but as an idea it could be at least thought of. Sounds a little bit crazy though, I recognize it :).</li>
</ul></div><div><blockquote type="cite"><div class="h5"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span style="color:rgb(34,34,34)"></span></div></div></div></div></blockquote></div></div>
</blockquote></div><div class="gmail_extra">When you have stable and accurate documents of this sort, let's talk. You may have noticed that few (any?) of the recent major API revs are documented in this manner…</div>
</div></div></blockquote><br></div><div>There’s still something to work on for us.. As far as what I’ve written, just a crazy idea that came to my mind. After all, everyone’s phone has lots of things that were considered crazy years ago.</div><br></body></html>