On 17 Jan 2014, at 22:06, Robert Collins <[email protected]> wrote:
> On 17 January 2014 09:22, Renat Akhmerov <[email protected]> wrote: >> Since it’s pretty easy to get lost among all the opinions I’d like to >> clarify/ask a couple of things: >> >> Keeping all the clients physically separate/combining them in to a single >> library. Two things here: >> >> In case of combining them, what exact project are we considering? If this >> list is limited to core projects like nova and keystone what policy could we >> have for other projects to join this list? (Incubation, graduation, >> something else?) >> 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. >> >> 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 :). > > Launchpadlib which builds on wadllib did *exactly* that. It worked > fairly well with the one caveat that it fell into the ORM trap - just > in time lookups for everything with crippling roundtrips. > Thanks, I’ll have a look at it.
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
