canmove, Confirmed users
1,173
edits
Services/Sync/Protocol 2.0 changes: Difference between revisions
Jump to navigation
Jump to search
Services/Sync/Protocol 2.0 changes (view source)
Revision as of 17:37, 19 January 2012
, 19 January 2012→Proposed changes to migrate to 2.0
No edit summary |
|||
| Line 3: | Line 3: | ||
browserid support | browserid support | ||
* token server and metadata tokens | * token server and metadata tokens | ||
* remove username from urls? | |||
max individual request size | max individual request size | ||
* right now we limit (not implemented in python!) wbo size, but not total size. Restrict post body size to 1M? | * right now we limit (not implemented in python!) wbo size, but not total size. Restrict post body size to 1M? Do this at Zeus level? What is the spec for return values. Overall post body size, including chunked overhead? | ||
drop parentid | drop parentid | ||
| Line 12: | Line 13: | ||
return milliseconds since epoch | return milliseconds since epoch | ||
* figure out how to get the timestamp into integer precision | * figure out how to get the timestamp into integer precision for internal storage | ||
405 for wrong method | 405 for wrong method | ||
* Cornice probably buys us this directly | * Cornice probably buys us this directly | ||
304 not modified when X- | 304 not modified when X-If-Unmodified-Since < current | ||
* Saves processing the request body | * Saves processing the request body | ||
| Line 23: | Line 24: | ||
generate better docs for how to implement backoff on client | generate better docs for how to implement backoff on client | ||
==Proposed changes to migrate to 2.1== | ==Proposed changes to migrate to 2.1== | ||