Revision 8cb45c13 docs/source/devguide.rst
b/docs/source/devguide.rst | ||
---|---|---|
25 | 25 |
========================= ================================ |
26 | 26 |
Revision Description |
27 | 27 |
========================= ================================ |
28 |
0.3 (June 10, 2011) Allow for publicly available objects via ``https://hostname/public``. |
|
28 |
0.3 (June 14, 2011) Large object support with ``X-Object-Manifest``. |
|
29 |
\ Allow for publicly available objects via ``https://hostname/public``. |
|
29 | 30 |
\ Support time-variant account/container listings. |
30 | 31 |
\ Add source version when duplicating with PUT/COPY/MOVE. |
31 | 32 |
\ Request version in object HEAD/GET requests (list versions with GET). |
... | ... | |
689 | 690 |
* Time-variant account/container listings via the ``until`` parameter. |
690 | 691 |
* Object versions - parameter ``version`` in HEAD/GET (list versions with GET), ``X-Object-Version-*`` meta in replies, ``X-Source-Version`` in PUT/COPY/MOVE. |
691 | 692 |
* Publicly accessible objects via ``https://hostname/public``. Control with ``X-Object-Public``. |
693 |
* Large object support with ``X-Object-Manifest``. |
|
692 | 694 |
|
693 | 695 |
Clarifications/suggestions: |
694 | 696 |
|
... | ... | |
700 | 702 |
* Container/object lists use a ``200`` return code if the reply is of type json/xml. The reply will include an empty json/xml. |
701 | 703 |
* In headers, dates are formatted according to RFC 1123. In extended information listings, dates are formatted according to ISO 8601. |
702 | 704 |
* The ``Last-Modified`` header value always reflects the actual latest change timestamp, regardless of time control parameters and version requests. Time precondition checks with ``If-Modified-Since`` and ``If-Unmodified-Since`` headers are applied to this value. |
703 |
* While ``X-Object-Manifest`` can be set and unset, large object support is not yet implemented (**TBD**).
|
|
705 |
* A ``HEAD`` or ``GET`` for an ``X-Object-Manifest`` object, will include modified ``Content-Length`` and ``ETag`` headers, according to the characteristics of the objects under the specified prefix. The ``Etag`` will be the MD5 hash of the corresponding ETags concatenated. In extended container listings there is no metadata processing.
|
|
704 | 706 |
|
705 | 707 |
The Pithos Client |
706 | 708 |
----------------- |
Also available in: Unified diff