SwiftNextAPI - Revision history

Zaitcev: Add the content-length in 204 thing under "Undisputed"

2016-05-18T16:30:13Z

Add the content-length in 204 thing under "Undisputed"

Samuel Merritt at 18:16, 20 May 2015

2015-05-20T18:16:04Z

Samuel Merritt at 18:40, 9 December 2013

2013-12-09T18:40:25Z

Samuel Merritt at 17:01, 6 December 2013

2013-12-06T17:01:12Z

Donagh McCabe: /* Fixes */

2013-03-21T14:34:50Z

‎Fixes

Redbo: /* Fixes */

2013-02-20T18:44:17Z

‎Fixes

Ryan Lane: Text replace - "NOTOC" to ""

2013-02-17T23:30:34Z

Text replace - "__NOTOC__" to ""

Davidhadas at 07:56, 8 February 2013

2013-02-08T07:56:15Z

Torgomatic at 19:02, 6 February 2013

2013-02-06T19:02:47Z

Chmouel: Add PATCH question

2013-01-24T12:55:54Z

Add PATCH question

@@ Line 18: / Line 18: @@
 * Unify account/container and object metadata POST semantics. In 1.0, POST /a[/c] adds new metadata, while POST /a/c/o replaces all existing metadata. Pick one. (Hint: keep the current container semantics and fix object semantics. Replace-all-metadata is much less common than a simple update.)
 * Fix status codes for HEAD responses. According to HTTP, the status code for GET and HEAD MUST match. (The headers SHOULD match, but we're not going to because it would slow things down a whole lot.)
 == Disputed Fixes ==
 * Use PATCH instead of POST for updating operations?
 * Add option to collapse slashes such that A/B//C///D will be treated as ('A','B','C','D') and not as ('A','B','','C','','','D')  - this is inline with the common URL normalization performed by web servers and not inline with the current practice of treating object names as opaque strings.

@@ Line 17: / Line 17: @@
 * Non-integer "limit" params are ignored; they should result in 400 responses. (Example: GET /v1/a/c?limit=the-sky). Happens for account and container listings.
 * Unify account/container and object metadata POST semantics. In 1.0, POST /a[/c] adds new metadata, while POST /a/c/o replaces all existing metadata. Pick one. (Hint: keep the current container semantics and fix object semantics. Replace-all-metadata is much less common than a simple update.)
 == Disputed Fixes ==
 * Use PATCH instead of POST for updating operations?
 * Add option to collapse slashes such that A/B//C///D will be treated as ('A','B','C','D') and not as ('A','B','','C','','','D')  - this is inline with the common URL normalization performed by web servers and not inline with the current practice of treating object names as opaque strings.

@@ Line 8: / Line 8: @@
 == New Features ==
 * encryption, to specify desired, algorithm (or should it be a default retrieved from the user token)
 == Fixes ==
 * Always quote Etag header value
-* Possibly change rate-limiting return code from 498 to 429 as per this rfc: http://tools.ietf.org/html/rfc6585  also see: https://bugs.launchpad.net/swift/+bug/1099365
+* Change rate-limiting return code from 498 to 429 as per this rfc: http://tools.ietf.org/html/rfc6585  also see: https://bugs.launchpad.net/swift/+bug/1099365
 * Remove vestigial "name" attribute of subdir elements in XML container listing.
 * Dates represented in ISO 8601 do not tell you that the time is in UTC, i.e., there should be a "Z" at end. Example: "2013-03-14T01:46:02.952040Z". As-is, it implies the dates are in local timezone.
 * Non-integer "limit" params are ignored; they should result in 400 responses. (Example: GET /v1/a/c?limit=the-sky). Happens for account and container listings.

← Older revision		Revision as of 17:01, 6 December 2013
Line 17:		Line 17:
	* Remove vestigial "name" attribute of subdir elements in XML container listing.		* Remove vestigial "name" attribute of subdir elements in XML container listing.
	* Dates represented in ISO 8601 do not tell you that the time is in UTC, i.e., there should be a "Z" at end. Example: "2013-03-14T01:46:02.952040Z". As-is, it implies the dates are in local timezone.		* Dates represented in ISO 8601 do not tell you that the time is in UTC, i.e., there should be a "Z" at end. Example: "2013-03-14T01:46:02.952040Z". As-is, it implies the dates are in local timezone.
		+	* Non-integer "limit" params are ignored; they should result in 400 responses. (Example: GET /v1/a/c?limit=the-sky). Happens for account and container listings.

← Older revision		Revision as of 14:34, 21 March 2013
Line 16:		Line 16:
	* Add option to collapse slashes such that A/B//C///D will be treated as ('A','B','C','D') and not as ('A','B','','C','','','D') - this is inline with the common URL normalization performed by web servers and not inline with the current practice of treating object names as opaque strings.		* Add option to collapse slashes such that A/B//C///D will be treated as ('A','B','C','D') and not as ('A','B','','C','','','D') - this is inline with the common URL normalization performed by web servers and not inline with the current practice of treating object names as opaque strings.
	* Remove vestigial "name" attribute of subdir elements in XML container listing.		* Remove vestigial "name" attribute of subdir elements in XML container listing.
		+	* Dates represented in ISO 8601 do not tell you that the time is in UTC, i.e., there should be a "Z" at end. Example: "2013-03-14T01:46:02.952040Z". As-is, it implies the dates are in local timezone.

← Older revision		Revision as of 18:44, 20 February 2013
Line 15:		Line 15:
	* Use PATCH instead of POST for updating operations?		* Use PATCH instead of POST for updating operations?
	* Add option to collapse slashes such that A/B//C///D will be treated as ('A','B','C','D') and not as ('A','B','','C','','','D') - this is inline with the common URL normalization performed by web servers and not inline with the current practice of treating object names as opaque strings.		* Add option to collapse slashes such that A/B//C///D will be treated as ('A','B','C','D') and not as ('A','B','','C','','','D') - this is inline with the common URL normalization performed by web servers and not inline with the current practice of treating object names as opaque strings.
		+	* Remove vestigial "name" attribute of subdir elements in XML container listing.

← Older revision		Revision as of 23:30, 17 February 2013
Line 1:		Line 1:
−	~~__NOTOC__~~	+
	This page is here to collect ideas for the next Swift API.		This page is here to collect ideas for the next Swift API.

← Older revision		Revision as of 07:56, 8 February 2013
Line 14:		Line 14:
	* Possibly change rate-limiting return code from 498 to 429 as per this rfc: http://tools.ietf.org/html/rfc6585 also see: https://bugs.launchpad.net/swift/+bug/1099365		* Possibly change rate-limiting return code from 498 to 429 as per this rfc: http://tools.ietf.org/html/rfc6585 also see: https://bugs.launchpad.net/swift/+bug/1099365
	* Use PATCH instead of POST for updating operations?		* Use PATCH instead of POST for updating operations?
		+	* Add option to collapse slashes such that A/B//C///D will be treated as ('A','B','C','D') and not as ('A','B','','C','','','D') - this is inline with the common URL normalization performed by web servers and not inline with the current practice of treating object names as opaque strings.

@@ Line 3: / Line 3: @@
 == Version ==
 * incremental update to the current API (1.1) or full new API (2.0) breaking 1.0 compatibility ?
-   - For the purposes of this, I would prefer to keep it as an incremental update to the current API. -- Chuck
+** - For the purposes of this, I would prefer to keep it as an incremental update to the current API. -- Chuck - +1 incremental -- Malini
 == New Features ==
@@ Line 12: / Line 10: @@
 == Fixes ==
 * Always quote Etag header value
 * Possibly change rate-limiting return code from 498 to 429 as per this rfc: http://tools.ietf.org/html/rfc6585  also see: https://bugs.launchpad.net/swift/+bug/1099365