René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Change Blob to eagerly get a BlobInfo if constructed with only id.","articleBody":"I wonder if in the cases where `BlobInfo` is not provided to `Blob` we should actually get it from the service, and use empty if not exists (and document that).\n\nMy reason is, considering the following `Blob` operations:\n`info`, `exists`, `content`, `update`, `delete`, `copyTo`, `reader`, `writer` and `signUrl`\n\nIn all cases info matters if options are used (created #252 for `exists` method) and in many cases info matters even without the options (e.g. `info`, `copyTo`).\nAlso, considering our example, I think this will make the API cleaner (and will not require\nthe explicit blob = blob.reload() pattern).\n\nThe reasons I think we don't want to force-get when BlobInfo is provided are:\n- we don't want to double-reload when our API is returning the Blob. I guess we can get around that with a \"special\" constructor...\n- That is the way for a user to force a new Info (e.g. for write).\n\nNow when we clearly separate between blob identity and blob metadata, I think it is not\nthat unexpected that if one supply the metadata we should respect it as is (though documentation should make it clear).\n\nThis issue was discussed in #251 and @mziccard suggested that instead of getting the info in the identity constructors (`BlobId` or bucket \u0026 name) to provide a `Blob.fetch(storage, identity)` methods and only have one constructor that accepts `BlobInfo` (no force loading in that one).\n\nI am in favor of the above suggestion though maybe we should name it `load` to be consistent with the existing `reload`.\n","author":{"url":"https://github.com/aozarov","@type":"Person","name":"aozarov"},"datePublished":"2015-10-13T21:00:26.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/253/google-cloud-java/issues/253"}