openstack/api-site
Code Issues Proposed changes

standardize capitalization: ReST -> REST

Browse Source 
source: http://en.wikipedia.org/wiki/Representational_state_transfer

Change-Id: If35339d1dc663c5b07a23bf62cb551bb29fe8037
This commit is contained in:
Jesse Andrews 2012-02-29 23:16:52 -08:00
parent 99d093fac8
commit 0d101b7afa
3 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.gitignore vendored
View File

@ -1,3 +1,3 @@
.DS_STORE?
.DS_Store
target/
*.xpr

8
doc/src/docbkx/openstack-api-site/src/wadls/compute-api/src/os-compute-devguide.xml
View File

@ -462,7 +462,7 @@
familiar with: </para>
<itemizedlist spacing="compact">
<listitem>
<para>ReSTful web services</para>
<para>RESTful web services</para>
</listitem>
<listitem>
<para>HTTP/1.1</para>
@ -565,7 +565,7 @@
<chapter xml:id="General_API_Information-d1e436">
<title>General API Information</title>
<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
HTTP protocol (methods, URIs, media types, response codes,
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
<parameter>Changes-Since</parameter> Parameter</title>
<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
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
<parameter>changes-since</parameter> parameter to
check for changes since a previous request. The

6
doc/src/docbkx/openstack-api-site/src/wadls/identity-api/src/admin/identity-admin.wadl
View File

@ -188,7 +188,7 @@
Authenticate to generate a token.
</p>
<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)
requires the inclusion of a specific authorization token HTTP x-header, defined as X-Auth-Token.
Clients obtain
@ -196,12 +196,12 @@
Keystone Service and supplying valid credentials.
</p>
<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
in the body.
</p>
<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.
</p>
</doc>