IMHOs on the API

Martin Povolny mpovolny at redhat.com
Thu Jan 17 09:50:58 UTC 2013


On Wed, Jan 16, 2013 at 10:24:47AM -0800, Richard Su wrote:
> Thanks for the feedback Martin. We have the same concerns, please see
> comments below.
> 
> On 01/16/2013 06:09 AM, Martin Povolny wrote:
> >While I am at the writing mood today I would like to say a couple of
> >things to the API. All these are IMHOs so let's pretend there's a IMHO
> >in front of each point.
> >
> >i) the API implementation should start with what the consumer needs or
> >wants
> >
> >1) the client would want to start with launching things (deployment)
> >2) next the client would want to check if the thing he wanted to run
> >actually runs
> >3) next the client may want something else like list all the stuff he
> >has
> Create a deployment is one the next items we are tackling with the API.
> Callback support is also listed as an issue in github. More thinking needs
> to go into this to make sure it is robust and usable.
> All of the endpoints have an #index action. Did you mean something else in
> (3)?

I just meant that first there is 1) then there is 2) and then there's
nothing for long time and then there's 3).

And we seem to start with 3).

Please remember the IMHO ;-)

<SNIP>

-- 
Martin Povolny <mpovolny at redhat.com>
tel. +420777714458


More information about the aeolus-devel mailing list