René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Discussion: discovery doc caching","articleBody":"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.\n\nWhen Cloud Pub/Sub released the API version v1, I started to cache ([appengine](https://github.com/GoogleCloudPlatform/cloud-pubsub-samples-python/blob/5ea5c39f74e7644feeff2d5e81df5b9549ce3c6b/appengine-push/discovery_doc.py)/[other](https://github.com/GoogleCloudPlatform/cloud-pubsub-samples-python/blob/5ea5c39f74e7644feeff2d5e81df5b9549ce3c6b/cmdline-pull/discovery_doc.py)) the discovery document in our samples.\n\nIt 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.\n\nBefore I proceed, I'd like to ask: Which do you guys prefer?\n","author":{"url":"https://github.com/tmatsuo","@type":"Person","name":"tmatsuo"},"datePublished":"2015-06-29T17:48:50.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/110/google-api-python-client/issues/110"}