René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"DISCUSSION: abstractions of service calls in storage","articleBody":"Generally speaking, the library functions seem to abstract when service interactions occur from the user.  In other words, some operations are local to the object (e.g [acl.grant](https://github.com/GoogleCloudPlatform/gcloud-python/blob/master/gcloud/storage/acl.py#L125)), others interact with the service (e.g. [acl.save](https://github.com/GoogleCloudPlatform/gcloud-python/blob/master/gcloud/storage/acl.py#L414)), while still others interact only some of the time (e.g. [bucket.default_object_acl](https://github.com/GoogleCloudPlatform/gcloud-python/blob/master/gcloud/storage/bucket.py#L124)).\nIf you're going to follow this model (and I'm not sure you should), I think you need to add preconditions to most service calls to ensure that confusing things don't happen. \nA good example of this would be the save and reload functions in the ACL class.  When should the user call reload()?  I don't think it's clear.  What happens when the user calls save() but the target ACL has changed on the service side since we last loaded it?  \n\nThis abstraction is especially dangerous because it works very well when a single client is involved but creates subtle problems when deployed at scale.\n\n/cc @thobrla \n","author":{"url":"https://github.com/silvolu","@type":"Person","name":"silvolu"},"datePublished":"2015-01-14T19:21:17.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/545/google-cloud-python/issues/545"}