Stephen

Nope, this was definitely you.

_From @callmehiphop on November 1, 2017 17:54_ @stephenplusplus are there any reasons why we hardcode the polling interval and/or don't use a back off in operations?

I think that makes sense, although I can't find any official recommendations from the Google API docs. Do you know of any @c0b, or best practices in general for what...

_From @c0b on November 3, 2017 17:19_ I did a search "best practices backing off strategy site:cloud.google.com" got this doc on storage, and indeed saw more places (like errors trouble...

_From @c0b on November 3, 2017 17:31_ the `(wait+=wait/2)` isn't exactly exponential backoff described in the storage/docs/exponential-backoff link above, it is `(wait*=1.5)` but easy to change to `Math.min(maxwait, wait*=2)`

The only thing I'm stuck on is we are talking about polling as opposed to error handling. We aren't retrying in the traditional sense, where the first request failed, so...

_From @callmehiphop on November 3, 2017 18:37_ I think that's fine, should we make a setter of some kind to allow users to configure these options? ```js operation .setPollingOptions({ retryDelayMultiplier:...

That sounds nice, how would we handle the methods that handle job polling internally, e.g. https://github.com/GoogleCloudPlatform/google-cloud-node/blob/7160d17a3b3c0f3af4bff900cc9ac64831564498/packages/bigquery/src/table.js#L377? Accept a new option, like `metadata.backoffSettings`?

Thank you for opening this, @c0b! I think we're okay on integer & timestamp precision, since it is available through the raw `apiResponse` argument when the user requires it. @callmehiphop...

_From @callmehiphop on October 10, 2016 19:55_ Maybe in the docs we could recommend/show examples for precision using an int64 lib? We use [node-int64](https://www.npmjs.com/package/node-int64) in Bigtable.