René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Should we make Project a real thing in gcloud? Particular for gcloud.storage?","articleBody":"Our discussions in the past have said that we want `Connection` to remain stateless and really just handle sending data over the wire as well as authentication.\n\nHowever, if you think about it, now that we're planning to push the \"transformation\" (from Python objects -\u003e JSON) down to Buckets, Blobs, and ACLs, the connection object isn't really just doing transport, it's also representing a connection to a specific project.\n\nDo you guys think it's worthwhile to make \"project\" a first-class citizen so that it makes more sense to do things like `project.get_all_buckets()` ?\n\nThis leads to a question of \"what is the relationship with connections and projects? We could have a one-to-one between them (where what you really do is instantiate a project and under the hood it instantiates a connection which handles auth, etc). Or we could have a singleton connection that all the projects use with their own set of credentials...?\n\nI am +0 on doing this kind of thing, and only just thought of it now given we need a \"clean\" place to put `get_all_buckets()` -- so feel free to close out as \"stfu, that's dumb\".\n\n/cc @dhermes \n","author":{"url":"https://github.com/jgeewax","@type":"Person","name":"jgeewax"},"datePublished":"2015-02-10T12:48:29.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/613/google-cloud-python/issues/613"}