On Jun 11, 2013, at 23:57, "Dustin J. Mitchell" <[email protected]> wrote:
> On Tue, Jun 11, 2013 at 9:52 PM, michael hancock <[email protected]> wrote: >> 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. > > True, but the URI structure is also versioned, so the entities at a > URI will change from version to version. In other words, ../api/nodes > may mean something completely different, or even be meaningless, in > API version 3. If .../api/nodes is no longer defined in v3 then: get .../api/nodes Accept: version=3 :returns 404 -- 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.
