openstack-attic/object-api
Code Issues Proposed changes

Corrects Cloud Files use

Browse Source 
Change-Id: Ice394c25d0f6c17b3d46d2523dd62433ea12f68f
This commit is contained in:
annegentle 2013-09-27 10:24:41 -05:00
parent 41aef0c7a6
commit 129493f305
2 changed files with 60 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

36
openstack-object-storage-dev/section_object-api-storage-object-svc.xml
View File

@ -163,14 +163,12 @@ format="SVG" scale="60"/>
are not required to include the ETag header, but it is
recommended to ensure that the storage system successfully
stored your object's content.</para>
<para>You can cause an object to expire after a certain date
by using the <code>X-Delete-At</code> or
<code>X-Delete-After</code> headers during an object
&PUT; operation. When Cloud Files detects one of these
headers, the system automatically stops serving that
object at the specified time and shortly after the
expiration date, it removes the object from the storage
system. </para>
<para>You can cause an object to expire after a certain date by using
the <code>X-Delete-At</code> or <code>X-Delete-After</code> headers
during an object &PUT; operation. When Object Storage detects one of
these headers, the system automatically stops serving that object at
the specified time and shortly after the expiration date, it removes
the object from the storage system. </para>
<para>The HTTP response will include the MD5 checksum of the
data written to the storage system. If you do not send the
ETag in the request, you should compare the value returned
@ -581,13 +579,12 @@ format="SVG" scale="60"/>
</section>
<section xml:id="assigning-cors-headers-to-requests">
<title>Assigning CORS Headers to Requests</title>
<para>CORS is a specification that stands for Cross-Origin
Resource Sharing. It defines how browsers and servers
communicate across origins using HTTP headers, such as
those assigned by Cloud Files API requests. These headers
are supported with the Cloud Files API. You can read more
about the definition of the Access-Control- response
headers and Origin response header at <link
<para>CORS is a specification that stands for Cross-Origin Resource
Sharing. It defines how browsers and servers communicate across
origins using HTTP headers, such as those assigned by Object Storage
API requests. These headers are supported with the Object Storage
API. You can read more about the definition of the Access-Control-
response headers and Origin response header at <link
xlink:href="http://www.w3.org/TR/access-control/"
>www.w3.org/TR/access-control/</link>.<itemizedlist>
<listitem>
@ -618,11 +615,10 @@ format="SVG" scale="60"/>
<para>You can assign these headers to objects only. </para>
<example>
<title>Assign CORS Header HTTP Request</title>
<para>In the example, the origin header is assigned that
indicates where the file came from. This allows you to
provide security that requests to your Cloud Files
repository are indeed from the correct
origination:</para>
<para>In the example, the origin header is assigned that indicates
where the file came from. This allows you to provide security
that requests to your Object Storage repository are indeed from
the correct origination:</para>
<literallayout class="monospaced"><xi:include href="samples/object-assign-cors-header-req.txt" parse="text"/></literallayout>
</example>
</section>

44
openstack-object-storage-dev/src/docbkx/object-api-language-bindings.xml Normal file
View File

@ -0,0 +1,44 @@
<?xml version="1.0" encoding="UTF-8"?>
<section xmlns="http://docbook.org/ns/docbook"
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
xml:id="language-specific-api-bindings">
<title>Language-Specific API Bindings</title>
<para>A set of supported API bindings in several popular languages are available from the
Rackspace Cloud Files product, which uses OpenStack Object Storage code for its
implementation. These bindings provide a layer of abstraction on top of the base REST
API, allowing programmers to work with a container and object model instead of working
directly with HTTP requests and responses. These bindings are free (as in beer and as in
speech) to download, use, and modify. They are all licensed under the MIT License as
described in the COPYING file packaged with each binding. If you do make any
improvements to an API, you are encouraged (but not required) to submit those changes
back to us.</para>
<para>The API bindings for Rackspace Cloud Files are hosted at <link
xlink:href="http://github.com/rackspace">http://github.com/rackspace</link>. Feel
free to coordinate your changes through github or, if you prefer, send your changes to
cloudfiles@rackspacecloud.com. Just make sure to indicate which language and version you
modified and send a unified diff.</para>
<para>Each binding includes its own documentation (either HTML, PDF, or CHM). They also
include code snippets and examples to help you get started. The currently supported API
binding for OpenStack Object Storage are:</para>
<itemizedlist>
<listitem>
<para>PHP (requires 5.x and the modules: cURL, FileInfo, mbstring)</para>
</listitem>
<listitem>
<para>Python (requires 2.4 or newer)</para>
</listitem>
<listitem>
<para>Java (requires JRE v1.5 or newer)</para>
</listitem>
<listitem>
<para>C#/.NET (requires .NET Framework v3.5)</para>
</listitem>
<listitem>
<para>Ruby (requires 1.8 or newer and mime-tools module)</para>
</listitem>
</itemizedlist>
<para>There are no other supported language-specific bindings at this time. You are welcome
to create your own language API bindings and we can help answer any questions during
development and give you full credit for your work.</para>
</section>