Open Stack

>
> 3. Could you describe the most complicated use case that your single-call
>> API supports? Again, please be very specific here.
>>
>> Same data can be derived from the link above.
>>
>>
> Ok, I'm actually not seeing and complicated examples, but I'm guessing
> that any attributes at the top of the page could be expanded on according
> the the syntax described.
>
> Hmmm...  one of the draw-backs I see with a "one-call" approach is you've
> got to have really good syntax checking for everything right from the
> start, or (if you plan to handle primitives one at a time) a really solid
> roll-back strategy if anything fails or has problems, cleaning up any
> primitives that might already have been created before the whole call
> completes.
>
> The alternative is to not do this with primitives... but then I don't see
> how that's possible either. (And certainly not easy to write tests for:
>  The great thing about small primitives is their methods tend to be easier
> to unit test.)
>

These are the good arguments! That's why I'd like to actually see the code
(even simplified approach will could work as a first step), i thing it
could do a lot of things clearer.

Thanks,
Eugene.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140418/fd3bcda6/attachment.html>