On Thu, May 5, 2011 at 4:12 AM, Jason Erickson <jason_at_jasonerickson.com> wrote:
> From a URL perspective, I have seen the version included in the path. For
> example: http://domain.com/ws/v1/people and http://domain.com/ws/v2/people
> would point to two versions of the API.
> However, that is just a small part of the problem. I would also be very
> interested in best practices used by others who are using Jersey and JAXB to
> implement the versioning scheme described above (or any other version scheme
> that people use to solve this problem).
For what it is worth, inclusion of version indicator in path is what I
use at work (and is codified as the mandated way to do it for both
internal and external services). To me this makes sense same way as
does versioning of URIs used for xml schema definitions, such that
given path is immutable at least with respect to backwards
compatibility.
-+ Tatu +-