[openstack-dev] a "common" client library

Dean Troyer dtroyer at gmail.com
Thu Jan 16 16:06:59 UTC 2014


On Thu, Jan 16, 2014 at 9:37 AM, Jesse Noller <jesse.noller at rackspace.com>wrote:

> On Jan 16, 2014, at 9:26 AM, Justin Hammond <justin.hammond at RACKSPACE.COM>
> wrote:
>
> I'm not sure if it was said, but which httplib using being used (urllib3
> maybe?). Also I noticed many people were talking about supporting auth
> properly, but are there any intentions to properly support 'noauth'
> (python-neutronclient, for instance, doesn't support it properly as of
> this writing)?
>
> Can you detail out noauth for me; and I would say the defacto httplib in
> python today is python-requests - urllib3 is also good but I would say from
> a *consumer* standpoint requests offers more in terms of usability /
> extensibility
>

requests is built on top of urllib3 so there's that...

The biggest reaon I favor using Jamie Lennox's new session layer stuff in
keystoneclient is that it better reflects the requests API instead of it
being stuffed in after the fact.  And as the one responsible for that
stuffing, it was pretty blunt and really needs to be cleaned up more than
Alessio did.

only a few libs (maybe just glance and swift?) don't use requests at this
point and I think the resistance there is the chunked transfers they both
do.

I'm really curious what 'noauth' means against APIs that have few, if any,
calls that operate without a valid token.

dt

-- 

Dean Troyer
dtroyer at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140116/00fee542/attachment.html>


More information about the OpenStack-dev mailing list