search

stravid / hulkort

Track and save your Git commit statistics
hulkort.com
1 stars 0 forks source link

Versioning our API #33

Open tombu opened 12 years ago

tombu commented 12 years ago

Is this a important point for us? Until now we only used the API to receive POST requests but at the moment it seems like the API starts growing. So I thought about about versioning the API. What do you think about it?

very good comment: http://stackoverflow.com/questions/389169/best-practices-for-api-versioning some thoughts (presumably a bit too much for us) but very interesting point of view ( -> watch screencast if you like): http://blog.apigee.com/detail/managing_multiple_apis_with_api_virtualization/

stravid commented 12 years ago

Disclaimer: I just read the Stackoverflow comment.

I like the idea of the base URL which always points to the state of the art version of our API. Plus the specific versions for deprecated API versions. But as far as I can tell, currently we don't have to change the API version right?

tombu commented 12 years ago

No, hopefully we don´t need to change the version right now. I just want to keep it in mind for future decisions concerning the structure of our API extensions.

Just like you I like the 'base URL idea'. So after I heard your opinion I think there´s currently no need for action, is it?

stravid commented 12 years ago

Don't think so!