2016-07-04 12:40 GMT+03:00 Antoni Segura Puimedon <
toni+openstac...@midokura.com>:

>
>
> On Mon, Jul 4, 2016 at 11:16 AM, Julien Danjou <jul...@danjou.info> wrote:
>
>> On Sun, Jun 26 2016, Denis Makogon wrote:
>>
>> > I know that some work in progress to bring Python 3.4 compatibility to
>> > backend services and it is kinda hard question to answer, but i'd like
>> to
>> > know if there are any plans to support asynchronous HTTP API client in
>> the
>> > nearest future using aiohttp [1] (PEP-3156)?
>>
>
> We were not sure if aiohttp would be taken in as a requirement, so in our
> kuryr kubernetes
> prototype we did our own asyncio http request library (it only does GET
> for now)[2]
>
> <https://github.com/midonet/kuryr/blob/k8s/kuryr/raven/aio/methods.py>
>

Good to see that someone already using async features. But i'd doubt
regarding re-inventing wheel, aiohttp is good choice for implementing both
clients and servers, so going deeper to asyncio core parts is required when
you're doing something very protocol-specific on the transport layer.

So, current question is about have common part of code that utilizes async
HTTP coroutines for current SDKs, and unfortunately, backward compatibility
should remain because not all projects were shifted to Py34 or greater yet,
but pace of feature deliver should remain as is.


>
>
>>
>> I don't think there is unfortunately. Most clients now relies on
>> `requests', and unfortunately it's not async not it seems ready to be
>> last time I checked.
>>
>
> for the neutron clients now we use a thread executor from the asyncio loop
> any time
> we do neutron client request.
>
> [2] https://github.com/midonet/kuryr/blob/k8s/kuryr/raven/aio/methods.py
>
>>
>> --
>> Julien Danjou
>> // Free Software hacker
>> // https://julien.danjou.info
>>
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to