Ken'ichi, thanks for the detail. I just added that summit session to my
list to attend. I'm looking forward to it.
On Thu, May 1, 2014 at 12:34 AM, Ken'ichi Ohmichi ken1ohmi...@gmail.comwrote:
Hi,
2014-04-29 10:28 GMT+09:00 Matthew Farina m...@mattfarina.com:
*3. Where would JSON
Hi,
2014-04-29 10:28 GMT+09:00 Matthew Farina m...@mattfarina.com:
*3. Where would JSON schemas come from?*
It depends on each OpenStack service. Glance and Marconi (soon) offer
schemas directly through the API - so they are directly responsible for
maintaining this - we'd just consume
Thanks Matt for bringing up these questions - I think having this kind of
discussion is essential for such a big idea. It also helps me clarify my own
thinking towards this issue.
Before I answer, I want to point out that I'm not staunchly for or against any
particular idea. I do think that
While reading this it struck me that we should prioritize the experience of
end-user, that is application developers, over the experience of those
working on the SDK. I don't think we'd ever directly talked about this so I
wanted to take a moment and state it.
What I put in below isn't my full
Jamie, thanks for going into so much detail.
On Mon, Apr 28, 2014 at 9:28 PM, Matthew Farina m...@mattfarina.com wrote:
While reading this it struck me that we should prioritize the experience
of end-user, that is application developers, over the experience of those
working on the SDK. I
Yes, thanks Jamie for the very thorough write ups and Matt for the thoughtful
comments.
My comments are inline below. A point of clarification: I’m using “SDK authors”
to mean all of us who are building the SDK and I’m using “SDK consumers” to
mean the end-user developers who will be using the
Jamie (and whom ever else wants to jump in),
It's been proposed to use json schema to describe the API calls rather
than code. The operations to perform and what they do would be
described rather than coded and then some code would use the schema to
know how to act.
Others are already doing
