standardize capitalization: ReST -> REST
source: http://en.wikipedia.org/wiki/Representational_state_transfer Change-Id: If35339d1dc663c5b07a23bf62cb551bb29fe8037
This commit is contained in:
parent
99d093fac8
commit
0d101b7afa
2
.gitignore
vendored
2
.gitignore
vendored
@ -1,3 +1,3 @@
|
|||||||
.DS_STORE?
|
.DS_Store
|
||||||
target/
|
target/
|
||||||
*.xpr
|
*.xpr
|
||||||
|
@ -462,7 +462,7 @@
|
|||||||
familiar with: </para>
|
familiar with: </para>
|
||||||
<itemizedlist spacing="compact">
|
<itemizedlist spacing="compact">
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>ReSTful web services</para>
|
<para>RESTful web services</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>HTTP/1.1</para>
|
<para>HTTP/1.1</para>
|
||||||
@ -565,7 +565,7 @@
|
|||||||
<chapter xml:id="General_API_Information-d1e436">
|
<chapter xml:id="General_API_Information-d1e436">
|
||||||
<title>General API Information</title>
|
<title>General API Information</title>
|
||||||
<para>
|
<para>
|
||||||
The OpenStack Compute API is defined as a ReSTful HTTP
|
The OpenStack Compute API is defined as a RESTful HTTP
|
||||||
service. The API takes advantage of all aspects of the
|
service. The API takes advantage of all aspects of the
|
||||||
HTTP protocol (methods, URIs, media types, response codes,
|
HTTP protocol (methods, URIs, media types, response codes,
|
||||||
etc.) and providers are free to use existing features of
|
etc.) and providers are free to use existing features of
|
||||||
@ -874,10 +874,10 @@ X-Auth-Token: eaaafd18-0fed-4b3a-81b4-663c99ec1cbb
|
|||||||
<title>Efficient Polling with the
|
<title>Efficient Polling with the
|
||||||
<parameter>Changes-Since</parameter> Parameter</title>
|
<parameter>Changes-Since</parameter> Parameter</title>
|
||||||
<para>
|
<para>
|
||||||
The ReST API allows you to poll for the status of
|
The REST API allows you to poll for the status of
|
||||||
certain operations by performing a &GET; on various
|
certain operations by performing a &GET; on various
|
||||||
elements. Rather than re-downloading and re-parsing
|
elements. Rather than re-downloading and re-parsing
|
||||||
the full status at each polling interval, your ReST
|
the full status at each polling interval, your REST
|
||||||
client may use the
|
client may use the
|
||||||
<parameter>changes-since</parameter> parameter to
|
<parameter>changes-since</parameter> parameter to
|
||||||
check for changes since a previous request. The
|
check for changes since a previous request. The
|
||||||
|
@ -188,7 +188,7 @@
|
|||||||
Authenticate to generate a token.
|
Authenticate to generate a token.
|
||||||
</p>
|
</p>
|
||||||
<p xmlns="http://www.w3.org/1999/xhtml">
|
<p xmlns="http://www.w3.org/1999/xhtml">
|
||||||
This call will return a token if successful. Each ReST request against other services (or other
|
This call will return a token if successful. Each REST request against other services (or other
|
||||||
calls on Keystone such as the GET /tenants call)
|
calls on Keystone such as the GET /tenants call)
|
||||||
requires the inclusion of a specific authorization token HTTP x-header, defined as X-Auth-Token.
|
requires the inclusion of a specific authorization token HTTP x-header, defined as X-Auth-Token.
|
||||||
Clients obtain
|
Clients obtain
|
||||||
@ -196,12 +196,12 @@
|
|||||||
Keystone Service and supplying valid credentials.
|
Keystone Service and supplying valid credentials.
|
||||||
</p>
|
</p>
|
||||||
<p xmlns="http://www.w3.org/1999/xhtml">
|
<p xmlns="http://www.w3.org/1999/xhtml">
|
||||||
Client authentication is provided via a ReST interface using the POST method,
|
Client authentication is provided via a REST interface using the POST method,
|
||||||
with v2.0/tokens supplied as the path. A payload of credentials must be included
|
with v2.0/tokens supplied as the path. A payload of credentials must be included
|
||||||
in the body.
|
in the body.
|
||||||
</p>
|
</p>
|
||||||
<p xmlns="http://www.w3.org/1999/xhtml">
|
<p xmlns="http://www.w3.org/1999/xhtml">
|
||||||
The Keystone Service is a ReSTful web service. It is the entry point to all service APIs.
|
The Keystone Service is a RESTful web service. It is the entry point to all service APIs.
|
||||||
To access the Keystone Service, you must know URL of the Keystone service.
|
To access the Keystone Service, you must know URL of the Keystone service.
|
||||||
</p>
|
</p>
|
||||||
</doc>
|
</doc>
|
||||||
|
Loading…
x
Reference in New Issue
Block a user