On Feb 2, 2018, at 2:11 AM, Duncan Thomas wrote:
>
> So I guess my question here is why is being RESTful good? Sure it's (very,
> very loosely) a standard, but what are the actual advantages? Standards come
> and go, what we want most of all is a good quality, easy to
As you said RESTful is not a standard but brings guidelines of good
practices. Which in turn doesn't preclude adding ideas, as long as
respecting RESTful approach. So we get from both sides.
Therefore a good schema structure adds to a de-facto standard, once the
practice is commonly used.
So I guess my question here is why is being RESTful good? Sure it's (very,
very loosely) a standard, but what are the actual advantages? Standards
come and go, what we want most of all is a good quality, easy to use API.
I'm not saying that going RESTful is wrong, but I don't see much discussion
On Jan 18, 2018, at 4:07 AM, TommyLike Hu wrote:
>Recently We found an issue related to our OpenStack action APIs. We
> usually expose our OpenStack APIs by registering them to our API Gateway (for
> instance Kong [1]), but it becomes very difficult when regarding to
> *From:* TommyLike Hu [mailto:tommylik...@gmail.com]
> *Sent:* January-18-18 5:07 AM
> *To:* OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>
> *Subject:* [openstack-dev] [api-wg] [api] [cinder] [nova] Support specify
> action
[mailto:tommylik...@gmail.com]
Sent: January-18-18 5:07 AM
To: OpenStack Development Mailing List (not for usage questions)
<openstack-dev@lists.openstack.org>
Subject: [openstack-dev] [api-wg] [api] [cinder] [nova] Support specify action
name in request url
Hey all,
Recently We found an issue r
Hey all,
Recently We found an issue related to our OpenStack action APIs. We
usually expose our OpenStack APIs by registering them to our API Gateway
(for instance Kong [1]), but it becomes very difficult when regarding to
action APIs. We can not register and control them seperately because