Dell DX6004S DX Object Storage Application Guide - Page 27

Scsp Read - computers

Page 27 highlights

Chapter 5. SCSP READ The following topics in this chapter discuss details about SCSP READ: • Section 5.1, "Introduction to READ" • Section 5.2, "Unnamed Object READ Details" • Section 5.3, "Normal Responses to READ" • Section 5.4, "Error Responses to READ" 5.1. Introduction to READ This section discusses general information about SCSP READ that applies to both named and unnamed objects. The READ message is a request for a specific content stream to be returned from a DX Storage cluster. It is formatted as a simple HTTP request using the GET method as shown in the following examples. • Named object: GET /mybucket/samplefile.txt HTTP/1.1 Host: cluster.example.com User-Agent: DX Storage Client/0.1 • Unnamed object: GET /12BFEA648C2697A56FD5618CAE15D5CA HTTP/1.1 Host: cluster.example.com User-Agent: DX Storage Client/0.1 DX Storage makes no assumptions about User-Agent (except that it is an HTTP/1.1 client). The Host header is mandatory and must conform to the requirements of Section 14.23 of the HTTP/1.1 specification. 5.1.1. Reading With Content Validation To validate the stream content as it is being read, you must add the query argument ? validate=yes to the URI. The content digest is then be computed and compared at the end. A hash mismatch will cause the socket connection to be dropped before the final bytes are sent. GET /name-or-uuid?validate=yes HTTP/1.1 Host: cluster.example.com User-Agent: DX Storage Client/0.1 5.1.2. Requestion Node Status and Cluster Capacity A READ request can be submitted without a name or UUID as follows to return counts for high-level node operations (read, write, delete, and so on), as well as cluster-wide Space Available and Total Capacity values. This information is also available on the Node Status page shown when navigating to a node's IP address with the designated SCSP port (for example, http://192.168.99.100:80). GET / HTTP/1.1 Host: cluster.example.com Copyright © 2010 Caringo, Inc. All rights reserved 22 Version 5.0 December 2010

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81

Copyright © 2010 Caringo, Inc.
All rights reserved
22
Version 5.0
December 2010
Chapter 5. SCSP READ
The following topics in this chapter discuss details about SCSP READ:
Section 5.1, “Introduction to READ”
Section 5.2, “Unnamed Object READ Details”
Section 5.3, “Normal Responses to READ”
Section 5.4, “Error Responses to READ”
5.1. Introduction to READ
This section discusses general information about SCSP READ that applies to both named and
unnamed objects.
The READ message is a request for a specific content stream to be returned from a DX Storage
cluster. It is formatted as a simple HTTP request using the GET method as shown in the following
examples.
Named object:
GET /mybucket/samplefile.txt HTTP/1.1
Host: cluster.example.com
User-Agent: DX Storage Client/0.1
Unnamed object:
GET /12BFEA648C2697A56FD5618CAE15D5CA HTTP/1.1
Host: cluster.example.com
User-Agent: DX Storage Client/0.1
DX Storage makes no assumptions about User-Agent (except that it is an HTTP/1.1 client). The
Host header is mandatory and must conform to the requirements of
Section 14.23
of the HTTP/1.1
specification.
5.1.1. Reading With Content Validation
To validate the stream content as it is being read, you must add the query argument
?
validate=yes
to the URI. The content digest is then be computed and compared at the end. A
hash mismatch will cause the socket connection to be dropped before the final bytes are sent.
GET /
name-or-uuid
?validate=yes HTTP/1.1
Host: cluster.example.com
User-Agent: DX Storage Client/0.1
5.1.2. Requestion Node Status and Cluster Capacity
A READ request can be submitted without a name or UUID as follows to return counts for high-level
node operations (read, write, delete, and so on), as well as cluster-wide Space Available and Total
Capacity values. This information is also available on the Node Status page shown when navigating
to a node's IP address with the designated SCSP port (for example, http://192.168.99.100:80).
GET / HTTP/1.1
Host: cluster.example.com