versioning

Did we have a talk about versioning?

(Sorry if yes, but I did not find it with the mailing list search tool.)

There are 2 concepts might be part of the Hydra vocab:

 1.) API versioning

Afaik by non backward compatible changes it is better to add a new API
root with the major version number. What about the minor, revision and
build numbers?

 2.) resource versioning

By resource versioning there are data storage solutions (e.g. event
storage aggregate version) which generate a version number after
updating a resource. This version number should be part of the write
requests to prevent concurrency related issues, like overriding
previous updates with stale data by using PUT, etc... (It is pretty
simple, the server checks the resource version sent with the request
and if it does not equal with the current version of the resource,
then the server returns a proper error code, possibly 409.) Should
this version number be part of the hydra vocab?

Received on Thursday, 18 September 2014 23:29:58 UTC