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
discovery.build() is handy, but afaik, it should be avoided in any production systems, especially if the API is considered stable and you should cache the discovery document and re-use it.
When Cloud Pub/Sub released the API version v1, I started to cache (appengine/other) the discovery document in our samples.
It is great if there is a library, or even discovery.build() takes care of all the caching stuff under the cover, so I will start working on either of 1) create an independent library that does caching, or 2) create a PR to google-api-python-client.
Before I proceed, I'd like to ask: Which do you guys prefer?
The text was updated successfully, but these errors were encountered:
I'm open to a pull request in this project. Would the public API change at all? Would clients have to behave differently? What are the ways the new behavior could be accidentally misused, and what would the consequences be?
discovery.build() is handy, but afaik, it should be avoided in any production systems, especially if the API is considered stable and you should cache the discovery document and re-use it.
When Cloud Pub/Sub released the API version v1, I started to cache (appengine/other) the discovery document in our samples.
It is great if there is a library, or even discovery.build() takes care of all the caching stuff under the cover, so I will start working on either of 1) create an independent library that does caching, or 2) create a PR to google-api-python-client.
Before I proceed, I'd like to ask: Which do you guys prefer?
The text was updated successfully, but these errors were encountered: