womax/nova
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge "Fix typo, ReST -> REST"

Browse Source
This commit is contained in:
Jenkins
2016-01-05 21:52:12 +00:00
committed by Gerrit Code Review
parent baa88b5c06 f78030a8ad
commit c8b1b2178d
3 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
api-guide/source/general_info.rst
+1 -1
View File
@@ -2,7 +2,7 @@
Key Compute API Concepts Key Compute API Concepts
========================= =========================
The OpenStack Compute API is defined as a ReSTful HTTP service. The API The OpenStack Compute API is defined as a RESTful HTTP service. The API
takes advantage of all aspects of the HTTP protocol (methods, URIs, takes advantage of all aspects of the HTTP protocol (methods, URIs,
media types, response codes, etc.) and providers are free to use media types, response codes, etc.) and providers are free to use
existing features of the protocol such as caching, persistent existing features of the protocol such as caching, persistent
api-guide/source/index.rst
+2 -2
View File
@@ -17,7 +17,7 @@
Compute API Compute API
=========== ===========
The nova project has a ReSTful HTTP service called the OpenStack Compute API. The nova project has a RESTful HTTP service called the OpenStack Compute API.
Through this API, the service provides massively scalable, on demand, Through this API, the service provides massively scalable, on demand,
self-service access to compute resources. Depending on the deployment those self-service access to compute resources. Depending on the deployment those
compute resources might be Virtual Machines, Physical Machines or Containers. compute resources might be Virtual Machines, Physical Machines or Containers.
@@ -39,7 +39,7 @@ access to your own deployment, and you should also be familiar with the
following concepts: following concepts:
* OpenStack Compute service * OpenStack Compute service
* ReSTful HTTP services * RESTful HTTP services
* HTTP/1.1 * HTTP/1.1
* JSON data serialization formats * JSON data serialization formats
api-guide/source/polling_changes-since_parameter.rst
+2 -2
View File
@@ -2,9 +2,9 @@
Efficient polling with the Changes-Since parameter Efficient polling with the Changes-Since parameter
================================================== ==================================================
The ReST API allows you to poll for the status of certain operations by 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 performing a **GET** on various elements. Rather than re-downloading and
re-parsing the full status at each polling interval, your ReST client re-parsing the full status at each polling interval, your REST client
may use the *``changes-since``* parameter to check for changes since a may use the *``changes-since``* parameter to check for changes since a
previous request. The *``changes-since``* time is specified as an `ISO previous request. The *``changes-since``* time is specified as an `ISO
8601 <http://en.wikipedia.org/wiki/ISO_8601>`__ dateTime 8601 <http://en.wikipedia.org/wiki/ISO_8601>`__ dateTime