On Tuesday, June 11, 2013 9:26:06 PM UTC-4, Dustin J. Mitchell wrote: > On Tue, Jun 11, 2013 at 12:41 PM, Daniel Pittman > <[email protected]<javascript:>> > wrote: > >> There should be a /latest/ link that points to the latest API version, > >> too. If such a thing does not exist in PuppetDB, then I think that'd > >> be the better feature request to make. > > > > This would be a fundamental mistake, however. Why? > > > > Because if the API changes, your client isn't going to work! > > True, but this is what the OP asked for!
That is not what I asked for. The discussion is about alternative designs for handling REST API versioning. For REST API's I see versioning as content negotiation. For example, GET .../api/nodes Accept: version=2.0 is like asking for version 2.0 of the document at .../api/nodes. I don't necessarily want the latest version of .../api/nodes, but version 2.0 which my client knows how to handle. -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-dev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
