From 0d101b7afa347d773c45bbf04f67b4df721d0e6c Mon Sep 17 00:00:00 2001 From: Jesse Andrews Date: Wed, 29 Feb 2012 23:16:52 -0800 Subject: [PATCH] standardize capitalization: ReST -> REST source: http://en.wikipedia.org/wiki/Representational_state_transfer Change-Id: If35339d1dc663c5b07a23bf62cb551bb29fe8037 --- .gitignore | 2 +- .../src/wadls/compute-api/src/os-compute-devguide.xml | 8 ++++---- .../src/wadls/identity-api/src/admin/identity-admin.wadl | 6 +++--- 3 files changed, 8 insertions(+), 8 deletions(-) diff --git a/.gitignore b/.gitignore index b745d2b53..11d6e3f71 100644 --- a/.gitignore +++ b/.gitignore @@ -1,3 +1,3 @@ -.DS_STORE? +.DS_Store target/ *.xpr diff --git a/doc/src/docbkx/openstack-api-site/src/wadls/compute-api/src/os-compute-devguide.xml b/doc/src/docbkx/openstack-api-site/src/wadls/compute-api/src/os-compute-devguide.xml index d58232c1c..719a3805f 100644 --- a/doc/src/docbkx/openstack-api-site/src/wadls/compute-api/src/os-compute-devguide.xml +++ b/doc/src/docbkx/openstack-api-site/src/wadls/compute-api/src/os-compute-devguide.xml @@ -462,7 +462,7 @@ familiar with: - ReSTful web services + RESTful web services HTTP/1.1 @@ -565,7 +565,7 @@ General API Information - 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 Efficient Polling with the <parameter>Changes-Since</parameter> Parameter - 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 changes-since parameter to check for changes since a previous request. The diff --git a/doc/src/docbkx/openstack-api-site/src/wadls/identity-api/src/admin/identity-admin.wadl b/doc/src/docbkx/openstack-api-site/src/wadls/identity-api/src/admin/identity-admin.wadl index a6ded2ac1..af8dcff9e 100644 --- a/doc/src/docbkx/openstack-api-site/src/wadls/identity-api/src/admin/identity-admin.wadl +++ b/doc/src/docbkx/openstack-api-site/src/wadls/identity-api/src/admin/identity-admin.wadl @@ -188,7 +188,7 @@ Authenticate to generate a token.

- 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.

- 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.

- 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.