Closed Bug 418642 Opened 17 years ago Closed 17 years ago

Create versioning scheme for the API

Categories

(addons.mozilla.org Graveyard :: API, defect)

defect
Not set
critical

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: laura, Assigned: laura)

References

Details

Attachments

(1 file, 1 obsolete file)

In order to make non backwards compatible changes to the API, we need to introduce a versioning scheme. Right now URLs are of the form http://s.a.m.o/%LOCALE%/%APP%/api/call This will change for future versions to include a version number, probably something like http://s.a.m.o/%LOCALE%/%APP%/api/version/call Current URLs will remain valid but deprecated so we don't break Fx3b3.
Severity: normal → critical
Flags: blocking-firefox3?
Attached patch Basic versioning support (obsolete) — Splinter Review
Attachment #304749 - Flags: review?(morgamic)
Blocks: 417606
Attachment #304749 - Attachment is obsolete: true
Attachment #304749 - Flags: review?(morgamic)
I had a stupid logic error in the first patch. Try this instead.
Attachment #304754 - Flags: review?(morgamic)
Attachment #304754 - Flags: review?(morgamic) → review+
Fixed in r10615. The version number can be added directly after the API, e.g.: https://services.addons.mozilla.org/%LOCALE%/%APP%/[api_version]/api/search/foo The current version of the API to be used with Fx3 b4 is 0.9. If no version number is supplied it defaults to 0 which will be compatible with Fx3 b3. (ie nothing should break).
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Flags: blocking-firefox3?
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: