I would hope we'd develop small standardized routing plugins for our major web server platforms that map API versions to current_handlers, deprecated_handlers, and version_unsupported_handlers.
----- Original Message ----- From: "Richard Newman" <[email protected]> <snip> My only concern with the version-first idea: it can introduce some cost in deployment and software management. Nobody wants to maintain 30 different entry points to mostly-the-same code, just because you revved a version number to change some API contract. Ideally one can segment the URL space (or use back-compatibility somehow) to allow for sensible revving: foo.com/1/users/2/eat => {v: 5, name: "bar"} I'm a huge fan of "version everything", but I'm also mindful of the friction factor that it can impose along some axes. This is mainly an issue when you're dealing with deployed clients. <snip> _______________________________________________ Sync-dev mailing list [email protected] https://mail.mozilla.org/listinfo/sync-dev
