4 ms·
Great, I was wondering how to version my library once I reach 1.0. > 3: RESTful. It should speak the language of HTTP verbs: GET, PUT, POST, PATCH, UPDATE, DEL
by loup-vaillant 9y ago
Great, I was wondering how to version my library once I reach 1.0.
> 3: RESTful. It should speak the language of HTTP verbs: GET, PUT, POST, PATCH, UPDATE, DELETE.
Oh, it was talking about web interfaces. Oh well.
- deleted 9y ago[deleted]
- tracker1 9y agoIs there a reason you can't use semver? Or was this just a quippy remark?
- loup-vaillant 9y agoThis article isn't even about semantic versioning. It is exclusively about web API design and versioning, and the web doesn't interest me. API used to mean headers, types, Java interfaces… stuff programmers use to link code together. And now the web is hijacking the term to a point where regular APIs can't even be named. I mean, can web developers even think about this kind of API now? I bet this explains part of the microservice madness we've seen lately. If the only kind of API you know goes through a web server, of course you'd use not-so-micro-services to modularise your application.
- tracker1 9y agoMy point was, that if it came to versioning API library versions, then "just use semver" would seem to be the most appropriate answer. I understand the conflation between "web api" and "api" here, I feel the same when "Microsoft SQL Server" is referred to as simple "SQL Server"
- loup-vaillant 9y agoI do intend to "just use semver". I was just hoping this article would give me something more.