On 9/23/13 2:33 PM, Chris Karlof wrote:
Hi all,
The Firefox Account and supporting servers are in the process of implementing a
versioning strategy for API endpoints. Lloyd suggested that it would be a good
idea for all Identity services to use the same versioning strategy.
We're proposing that the API version is the first path element, e.g.,
https://some-server/1/some/api/call
alternatively,
https://some-server/v1/some/api/call
+1 I like v1 as it's descriptive.
Also, we'll need to have a versioning strategy for
* DOM APIs
* postMessage protocols
For internal DOM apis (which might be temporary), I've proposed[1] we
use the gecko version number in the API name.
-- ozten
[1]
https://groups.google.com/forum/#!searchin/mozilla.dev.identity/native$20storage$20proposal/mozilla.dev.identity/9iOC_K-Jnj4/01WKpidTqKsJ
Thoughts?
-chris
P.S. We didn't choose Accept headers because we don't have REST apis and they
are more cumbersome to deal with.
_______________________________________________
dev-identity mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-identity
_______________________________________________
Sync-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/sync-dev
