Open Stack

I found https://github.com/kennethreitz/requests/issues/713

"""
Lukasa<https://github.com/Lukasa> commented a month ago<https://github.com/kennethreitz/requests/issues/713#issuecomment-35594520>

There's been no progress on this, and it's not high on the list of priorities for any of the core development team. This is only likely to happen any time soon if someone else develops it. =)

"""

So maybe someone from openstack (or other) just needs to finish the above up?

From: Chuck Thier <cthier at gmail.com<mailto:cthier at gmail.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Friday, April 4, 2014 at 11:50 AM
To: OpenStack Development Mailing List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: Re: [openstack-dev] Issues with Python Requests

I think I have worked out the performance issues with eventlet and Requests with most of it being that swiftclient needs to make use of requests.session to re-use connections, and there are likely other areas there that we can make improvements.

Now on to expect: 100-continue support, has anyone else looked into that?

--
Chuck


On Fri, Apr 4, 2014 at 9:41 AM, Chuck Thier <cthier at gmail.com<mailto:cthier at gmail.com>> wrote:
Howdy,

Now that swift has aligned with the other projects to use requests in python-swiftclient, we have lost a couple of features.

1.  Requests doesn't support expect: 100-continue.  This is very useful for services like swift or glance where you want to make sure a request can continue before you start uploading GBs of data (for example find out that you need to auth).

2.  Requests doesn't play nicely with eventlet or other async frameworks [1].  I noticed this when suddenly swift-bench (which uses swiftclient) wasn't performing as well as before.  This also means that, for example, if you are using keystone with swift, the auth requests to keystone will block the proxy server until they complete, which is also not desirable.

Does anyone know if these issues are being addressed, or begun working on them?

Thanks,

--
Chuck

[1] http://docs.python-requests.org/en/latest/user/advanced/#blocking-or-non-blocking

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140404/35d21432/attachment.html>