Dell DX6004S DX Object Storage Application Guide - Page 20

Introduction to the Simple Content Storage, Protocol SCSP

Page 20 highlights

Chapter 4. Introduction to the Simple Content Storage Protocol (SCSP) The mechanism that applications use to communicate with DX Storage is a simple, text-based protocol based on the HyperText Transfer Protocol (HTTP). Referred to as the Simple Content Storage Protocol, or SCSP, its methods and syntax are a proper subset of the HTTP/1.1 standard. Although many of the optional parts of HTTP/1.1 are not implemented in SCSP (which is why the protocol is referred to as Simple), all required components of the protocol are implemented as well as several of the common methods. Moreover, DX Storage assumes communication with an HTTP/1.1 compliant client application. In DX Storage version 5.0 for the first time, SCSP supports authentication and authorization on all SCSP operations. For details, see Chapter 12, Introduction to Object Security . This chapter provides an overview of the most important parts of SCSP and how they map to HTTP. For details on the semantics and other nuances of HTTP, see the Hypertext Transfer Protocol - HTTP/1.1 specification. Developers wishing to write a native integration to DX Storage SCSP should also refer to the DX Storage Software Development Kit (SDK) Overview for information on the APIlevel implementation of the SCSP protocol, including complete source implementations of that API in several common languages (currently Java, Python, C++, and C#). See one of the following topics for more information: • Section 4.1, "Mapping SCSP Operations to HTTP Methods" • Section 4.2, "HTTP Overview" • Section 4.3, "Requests and Responses" • Section 4.4, "Formatting SCSP Commands for Named and Unnamed Objects" • Section 4.6, "Normal Response Headers" 4.1. Mapping SCSP Operations to HTTP Methods The following table maps SCSP operations to their complementary HTTP methods. SCSP operation READ INFO WRITE UPDATE DELETE APPEND COPY n/a n/a n/a HTTP method GET HEAD POST PUT DELETE n/a n/a TRACE CONNECT OPTIONS Copyright © 2010 Caringo, Inc. All rights reserved 15 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
15
Version 5.0
December 2010
Chapter 4. Introduction to the Simple Content Storage
Protocol (SCSP)
The mechanism that applications use to communicate with DX Storage is a simple, text-based
protocol based on the HyperText Transfer Protocol (HTTP). Referred to as the Simple Content
Storage Protocol, or
SCSP
, its methods and syntax are a proper subset of the HTTP/1.1 standard.
Although many of the optional parts of HTTP/1.1 are not implemented in SCSP (which is why the
protocol is referred to as
Simple
), all required components of the protocol are implemented as
well as several of the common methods. Moreover, DX Storage assumes communication with an
HTTP/1.1 compliant client application.
In DX Storage version 5.0 for the first time, SCSP supports authentication and authorization on all
SCSP operations. For details, see
Chapter 12,
Introduction to Object Security
.
This chapter provides an overview of the most important parts of SCSP and how they map to HTTP.
For details on the semantics and other nuances of HTTP, see the Hypertext Transfer Protocol –
HTTP/1.1 specification
. Developers wishing to write a native integration to DX Storage SCSP should
also refer to the DX Storage Software Development Kit (SDK) Overview for information on the API-
level implementation of the SCSP protocol, including complete source implementations of that API
in several common languages (currently Java, Python, C++, and C#).
See one of the following topics for more information:
Section 4.1, “Mapping SCSP Operations to HTTP Methods”
Section 4.2, “HTTP Overview”
Section 4.3, “Requests and Responses”
Section 4.4, “Formatting SCSP Commands for Named and Unnamed Objects”
Section 4.6, “Normal Response Headers”
4.1. Mapping SCSP Operations to HTTP Methods
The following table maps SCSP operations to their complementary HTTP methods.
SCSP operation
HTTP method
READ
GET
INFO
HEAD
WRITE
POST
UPDATE
PUT
DELETE
DELETE
APPEND
n/a
COPY
n/a
n/a
TRACE
n/a
CONNECT
n/a
OPTIONS