The application may be able to obtain a CRC32C checksum in some out-of-band way. For example, if the object was downloaded from some other cloud storage service, or because the application already queried the GCS object metadata. In these cases, providing the value to the client library improves the end-to-end data integrity verification.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-04-02 UTC."],[[["The page provides documentation for the `Crc32cChecksumValue` struct within the Google Cloud Storage C++ client library, spanning versions from 2.11.0 to the latest release candidate, 2.37.0-rc."],["Users can find links to the documentation for each specific version of the library, allowing for version-specific reference material, and can see the history of releases."],["The documentation covers the utility of pre-computed CRC32C checksums for enhanced data integrity verification, particularly when the checksum is obtained through external sources."],["The documentation includes details on a constructor `Crc32cChecksumValue()` and a static function `name()` within this struct, highlighting available operations."],["The documentation links to external research regarding data integrity verification, specifically citing a paper from the HotOS 2021 conference, offering further reading on the subject."]]],[]]
