versioning

[evillemez]

The serializer supports object versioning, which is specified in the serialization contexts when the serializer call is made. I think a potentially good way to allow a client some control over this is to be able to specify the version to use via a custom header.

Versioning of web apis is a huge can of worms - this isn't about versioning of resources (routes/interface) per se, it's more about versioning the representations of the objects returned, in whatever format.

HATEOAS may solve all versioning/evolution questions, but I'm not convinced it's a practical solution yet.

Worth a read, including the comments: http://www.mnot.net/blog/2011/10/25/web_api_versioning_smackdown?utm_content=bufferf07f9&utm_source=buffer&utm_medium=twitter&utm_campaign=Buffer