Versioning via content negotiation

[steveklabnik]

Hey guys-

This is more of a feature request than anything else. Here's the deal:

It's been kinda popular to version APIs by using some sort of prefix, like /v1/posts/1 vs /v2/posts/1. And this is bad. The Right Way is through content-negotiation. Most people go the prefix route because it's easy, and because it doesn't require a lot of work. That said, just like Rails made RESTful stuff easy, I'd love to see some work go into making the other parts of REST that Rails DOESN'T do be easy, too. And this would be part of it.

Anyway, I haven't dived into your code, and I don't think I'm going to have the time to work up a pull request of my own that'd do something like this, but you might want to think about it.