2016-07-04 13:22 GMT+03:00 Roman Podoliaka <[email protected]>:
> Denis, > > > Major problem > > appears when you trying to provision resource that requires to have some > > time to reach ACTIVE/COMPLETED state (like, nova instance, stack, trove > > database, etc.) and you have to use polling for status changes and in > > general polling requires to send HTTP requests within specific time frame > > defined by number of polling retries and delays between them (almost all > > PaaS solutions in OpenStack are doing it that might be the case of > > distributed backend services, but not for async frameworks). > > How would an asynchronous client help you avoid polling here? You'd > need some sort of a streaming API producing events on the server side. > > No, it would not help me to get rid of polling, but using async requests will allow to proceed with next independent async tasks while awaiting result on async HTTP request. > If you are simply looking for a better API around polling in OS > clients, take a look at https://github.com/koder-ua/os_api , which is > based on futures (be aware that HTTP requests are still *synchronous* > under the hood). > > Thanks, > Roman > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
