@clemensv @stilkov how should versioning of api's be done correctly then?
2
@YvesGoeleven @clemensv I don't even know what "versioning of the API" is supposed to mean. Version your format, relations, & documentation
1
1
@stilkov @YvesGoeleven "/v2/" says "all my resources changed in a breaking way all at once" - i.e. it's not a version but a different svc
6
9
5
@stilkov @clemensv @YvesGoeleven When DLL's version changes, it doesnt mean all classes/interfaces have breaking change - why API different?
1
@aliostad @stilkov @YvesGoeleven When the DLL version changes you will have to re-link/-bind it explicitly. The whole thing.
2
@clemensv @stilkov @YvesGoeleven but when you up version, it has passed that point. Similar to DLL. Same rule apply. I am for URL versioning
1
@aliostad @stilkov @YvesGoeleven 45 changes anywhere and you'll maintain 45 concurrent resource graphs at /v1/ through /v45/?
1
@clemensv @stilkov @YvesGoeleven depends on changes. Similar to DLL, we do not change the main version everytime we change something.
1
Replying to @aliostad
@aliostad @clemensv @yvesgoeleven You do not change all IDs of all entities stored in a DB when you update the schema

Dec 4, 2012 · 4:31 PM UTC

1
Replying to @stilkov
@stilkov @clemensv @YvesGoeleven in which case no need to change API version. For domain objects defined 5 axes inc ver byterot.blogspot.co.uk/2012/…