mcavage/node-restify — pull request #57 by warorface (2012-01-24 21:15:25+00:00)
Title: Range Versioning

Currently if I do a new API version that means I have to manually create routes for previous versions even though I haven't changed anything on other routes.

My use case

Server:

- Route A version >=1.1.0
- Route B version 1.2.0
- Route B version <=1.1.0

Client: Uses a unique version, sending:
0.9.9 - 1.2.1 - 1.1.0
Instead of:
>=0.9.8, <= 1.3.0, =1.2.1