Open Stack

On Mon, Mar 03, 2014 at 09:19:34AM +0100, Radomir Dopieralski wrote:
> On 27/02/14 11:52, Petr Blaho wrote:
> 
> > I agree with you w/r/t to indirection when accessing data but I like the
> > idea that when I look at json repsonse I see what type of resource it
> > is. That wrapper element describes it. And I do not need to know what
> > request (url, service, GET or POST...) triggered that output.
> 
> That's data denormalization. What do you then do when the two sources of
> information don't agree? Also, do you actually need the json at all
> without knowing where it came from (not just from which api call, but
> which system and at what time)? I can't imagine such a situation.

Yeah, I agree with you that not wrapped json data is better solution.
I just liked how wrapped data looks.
> 
> Finally, when you need to save a whole lot of json outputs and need to
> know where they come from, you traditionally put that information in the
> file name, no?
> 
> -- 
> Radomir Dopieralski
> 
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

My concern is that it looks like OpenStack does not have a "proper" way
how to format output json in APIs and it is on behalf of each project.

-- 
Petr Blaho, pblaho at redhat.com
Software Engineer