Revision 4a1c29ea docs/source/devguide.rst

b/docs/source/devguide.rst
25 25
=========================  ================================
26 26
Revision                   Description
27 27
=========================  ================================
28
0.7 (Oct 21, 2011)         Suggest upload/download methods using hashmaps.
28
0.7 (Nov 21, 2011)         Suggest upload/download methods using hashmaps.
29 29
\                          Propose syncing algorithm.
30 30
\                          Support cross-account object copy and move.
31 31
\                          Pass token as a request parameter when using ``POST`` via an HTML form.
......
33 33
\                          Use container ``POST`` to upload missing blocks of data.
34 34
\                          Report policy in account headers.
35 35
\                          Add insufficient quota reply.
36
\                          Use special meta to always report Merkle hash.
36 37
0.6 (Sept 13, 2011)        Reply with Merkle hash as the ETag when updating objects.
37 38
\                          Include version id in object replace/change replies.
38 39
\                          Change conflict (409) replies format to text.
......
437 438
content_encoding            The encoding of the object (optional)
438 439
content-disposition         The presentation style of the object (optional)
439 440
last_modified               The last object modification date (regardless of version)
441
x_object_hash               The Merkle hash
440 442
x_object_version            The object's version identifier
441 443
x_object_version_timestamp  The object's version timestamp
442 444
x_object_modified_by        The user that committed the object's version
......
600 602
Last-Modified               The last object modification date (regardless of version)
601 603
Content-Encoding            The encoding of the object (optional)
602 604
Content-Disposition         The presentation style of the object (optional)
605
X-Object-Hash               The Merkle hash
603 606
X-Object-Version            The object's version identifier
604 607
X-Object-Version-Timestamp  The object's version timestamp
605 608
X-Object-Modified-By        The user that comitted the object's version
......
695 698
Last-Modified               The last object modification date (regardless of version)
696 699
Content-Encoding            The encoding of the object (optional)
697 700
Content-Disposition         The presentation style of the object (optional)
701
X-Object-Hash               The Merkle hash
698 702
X-Object-Version            The object's version identifier
699 703
X-Object-Version-Timestamp  The object's version timestamp
700 704
X-Object-Modified-By        The user that comitted the object's version
......
979 983
* Multi-range object ``GET`` support as outlined in RFC2616.
980 984
* Object hashmap retrieval through ``GET`` and the ``format`` parameter.
981 985
* Object create via hashmap through ``PUT`` and the ``format`` parameter.
986
* The object's Merkle hash is always returned in the ``X-Object-Hash`` header.
982 987
* Object create using ``POST`` to support standard HTML forms.
983 988
* Partial object updates through ``POST``, using the ``Content-Length``, ``Content-Type``, ``Content-Range`` and ``Transfer-Encoding`` headers. Use another object's data to update with ``X-Source-Object`` and ``X-Source-Version``. Truncate with ``X-Object-Bytes``. New ETag corresponds to the Merkle hash of the object's hashmap.
984 989
* Include new version identifier in replies for object replace/change requests.

Also available in: Unified diff