That is a good thought. Currently we haven't thought of automatically trigger those blocked requests, and still expect users to manually trigger it.
Thanks -min On 12/20/12 7:52 AM, "Pranav Saxena" <pranav.sax...@citrix.com> wrote: >Amazon uses API throttling but from what I know they leverage the leaky >bucket algorithm and have some kind off a "back-off" algorithm for few >of their tasks in which the API requests which were throttles are >automatically triggered depending upon what the use case is . Hence I >thought that perhaps , we might also encounter a similar scenario in >cloudstack as well . Can anyone think off a certain use case pertaining >to Cloudstack which might require such a functionality ? > >Regards, >Pranav > >-----Original Message----- >From: John Kinsella [mailto:j...@stratosec.co] >Sent: Thursday, December 20, 2012 9:05 PM >To: cloudstack-dev@incubator.apache.org >Subject: Re: [DISCUSS]API request throttling > > >On Dec 20, 2012, at 2:20 AM, Pranav Saxena <pranav.sax...@citrix.com> > wrote: >> Also are we planning to build the code in such a way that when we take >>into consideration the "throttling time " , do we have some kind off a >>back-off algorithm to trigger the request again automatically ( may be >>in some scenarios , not sure though ) , when we're being throttled (like >>come back after a "restore rate" period, specific to the type of API >>request one is making ) or the user has to make the request again >>manually every time once he is throttled. This might sound vague but I >>am just curious to know if such a scenario can exist or not . > >Good point. > >
