<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 08/06/2013 10:54 AM, Dolph Mathews
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAC=h7gV67+i-H1aFvr+OzzmEK-QhyOHzZWORzZP6QxG9ryW5Ng@mail.gmail.com"
      type="cite">
      <div dir="ltr"><br>
        <div class="gmail_extra">
          <div class="gmail_quote">On Tue, Aug 6, 2013 at 9:28 AM, Jorge
            Williams <span dir="ltr"><<a moz-do-not-send="true"
                href="mailto:jorge.williams@rackspace.com"
                target="_blank">jorge.williams@rackspace.com</a>></span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div class="im"><br>
                On Aug 6, 2013, at 8:36 AM, Adam Young wrote:<br>
                <br>
                > On 08/06/2013 01:19 AM, Jamie Lennox wrote:<br>
                >> Hi all,<br>
                >><br>
                >> Partially in response to the trusts API review
                in keystoneclient<br>
                >> (<a moz-do-not-send="true"
                  href="https://review.openstack.org/#/c/39899/"
                  target="_blank">https://review.openstack.org/#/c/39899/</a>
                ) and my work on keystone API<br>
                >> version discoverability (spell-check disagrees
                but I'm going to assume<br>
                >> that's a word - <a moz-do-not-send="true"
                  href="https://review.openstack.org/#/c/38414/"
                  target="_blank">https://review.openstack.org/#/c/38414/</a>
                ) I was thinking<br>
                >> about how we should be able to know what/if an
                extension is available. I<br>
                >> even made a basic blueprint for how i think it
                should work:<br>
                >> <a moz-do-not-send="true"
href="https://blueprints.launchpad.net/python-keystoneclient/+spec/keystoneclient-extensions"
                  target="_blank">https://blueprints.launchpad.net/python-keystoneclient/+spec/keystoneclient-extensions</a>
                and then realized that GET /extensions is only a V2 API.<br>
                ><br>
                > I'm not certain that the extensions should really
                be in the v2 or v3.  It always seemed to me that
                Extensions should be parallel to, and separate from, the
                core API.<br>
                <br>
                <br>
              </div>
              I agree. Extensions should not be in core, but the
              mechanism by which extensions are discovered should be
              part of the core...right?<br>
            </blockquote>
            <div><br>
            </div>
            <div>Agree. The fact that you call GET /v2.0/extensions or
              GET /v3/extensions instead of GET /extensions just means
              that we can iterate on the "extensions" response itself,
              not necessarily that the extension *only* applies to
              particular version API being queried (that's a different
              issue).</div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    Agreed.  That makes sense.<br>
    <br>
    <br>
    So the APIs should be:<br>
    <br>
    v2.0/extensions<br>
    or<br>
    v3/extensions<br>
    <br>
    but those should return links to:<br>
    <br>
    extensions/some_extension<br>
    <br>
    <blockquote
cite="mid:CAC=h7gV67+i-H1aFvr+OzzmEK-QhyOHzZWORzZP6QxG9ryW5Ng@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div> </div>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <br>
              -jOrGe W.<br>
              <div class="HOEnZb">
                <div class="h5"><br>
                  <br>
                  _______________________________________________<br>
                  OpenStack-dev mailing list<br>
                  <a moz-do-not-send="true"
                    href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
                  <a moz-do-not-send="true"
                    href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
                    target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
                </div>
              </div>
            </blockquote>
          </div>
          <br>
          <br clear="all">
          <div><br>
          </div>
          -- <br>
          <div><br>
          </div>
          -Dolph
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
OpenStack-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>