You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Google suggests to use exponential backoff strategy for avoiding 4XX or 5XX errors. It can be implemented inside SDK and enabling by passing option to request constructor or request.execute. It would safe alot of time for developers who can't implement this strategy by some reasons.
The text was updated successfully, but these errors were encountered:
Check out my "ntil" NPM package. It makes exponential back-off very simple.
On 6 Nov 2015 2:56 am, "Vlad Tsepelev" notifications@github.com wrote:
Google suggests to use exponential backoff strategy for avoiding 4XX or
5XX errors. It can be implemented inside SDK and enabling by passing option
to request constructor or request.execute. It would safe alot of time for
developers who can't implement this strategy by some reasons.
—
Reply to this email directly or view it on GitHub #482.
Google suggests to use exponential backoff strategy for avoiding 4XX or 5XX errors. It can be implemented inside SDK and enabling by passing option to request constructor or request.execute. It would safe alot of time for developers who can't implement this strategy by some reasons.
The text was updated successfully, but these errors were encountered: