On Wed, Jun 12, 2013 at 1:11 AM, Mike Hancock <[email protected]> wrote:
> If .../api/nodes is no longer defined in v3 then:
>
>  get .../api/nodes
>  Accept: version=3
>
> :returns 404

Well, we've painted this bikeshed enough to get it through the winter.
 I don't expect to use the API myself, so I don't actually have much
concern with how this is done.

I think we're imagining different evolutions of the API.  For my part,
I'm working on a new API for Buildbot, where the v1 API's URI
structure doesn't correspond to the concepts in the new design.
There's no good mapping from v1 URIs to v2 URIs.  If I followed your
suggestion, then huge swathes of the URI space would appear and
disappear based on a content-negotiation header.  That's a pretty
serious violation of visibility, IMHO.  So, my URLs now have ../v2/..
in them.  I don't expect to ever create a version 3, but the option is
there if the design of the framework changes enough that the URI
structure is no longer appropriate.  And given how long the present
redesign is taking, that won't be for quite a while!

Dustin

-- 
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.


Reply via email to