referenceType property

Describes what the field reference contains. Possible string values are:

• "PATH" : Reference contains a GFS path or a local path.
• "BLOB_REF" : Reference points to a blobstore object. This could be either a v1 blob_ref or a v2 blobstore2_info. Clients should check blobstore2_info first, since v1 is being deprecated.
• "INLINE" : Data is included into this proto buffer
• "GET_MEDIA" : Data should be accessed from the current service using the operation GetMedia.
• "COMPOSITE_MEDIA" : The content for this media object is stored across multiple partial media objects under the composite_media field.
• "BIGSTORE_REF" : Reference points to a bigstore object
• "DIFF_VERSION_RESPONSE" : Indicates the data is stored in diff_version_response.
• "DIFF_CHECKSUMS_RESPONSE" : Indicates the data is stored in diff_checksums_response.
• "DIFF_DOWNLOAD_RESPONSE" : Indicates the data is stored in diff_download_response.
• "DIFF_UPLOAD_REQUEST" : Indicates the data is stored in diff_upload_request.
• "DIFF_UPLOAD_RESPONSE" : Indicates the data is stored in diff_upload_response.
• "COSMO_BINARY_REFERENCE" : Indicates the data is stored in cosmo_binary_reference.
• "ARBITRARY_BYTES" : Informs Scotty to generate a response payload with the size specified in the length field. The contents of the payload are generated by Scotty and are undefined. This is useful for testing download speeds between the user and Scotty without involving a real payload source. Note: range is not supported when using arbitrary_bytes.