...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
This overview of the Simple Content Storage Protocol (SCSP) methods explains how they map to the corresponding HTTP methods.
SCSP as a
...
Subset of HTTP
The mechanism that applications use to communicate with Swarm is a simple, text-based protocol based on HTTP. Known as theSimple Content Storage Protocol (SCSP), its the methods and syntax are a proper subset of the HTTP/1.1 standard.
...
Swarm assumes communication with an HTTP/1.1 compliant client application.
See the SDK Overview /wiki/spaces/DOCS/pages/2443822872 for the API-level implementation of SCSP. The SDK helps developers write integrations to Swarm. The SDK includes sample code in Java, Python, C++, and C#.
Mapping SCSP to HTTP
...
Methods
The following table maps SCSP methods to their complementary HTTP methods.
SCSP Method | HTTP Method | RFC 7231 Section |
|---|---|---|
GET | ||
HEAD | ||
POST | ||
PUT | ||
DELETE | ||
n/a |
| |
n/a |
| |
n/a |
| |
SCSP
...
Protocol
Most HTTP communication is initiated by a client application and consists of a request to be applied to an object on a Swarm server. In the simplest case, this is done This is performed using a single connection between the client application and the Swarm server. Being HTTP-based, SCSP protocol consists of HTTP requests and responses:
Requestsare generated by a Swarm client (that is, any HTTP/1.1 client), with these components:
Request method, with URI and protocol version
Case-insensitive query arguments
Required and optional headers
Responses are generated by one or more nodes in a storage cluster, with these components:
Status line, with the message's protocol version and a success or error code
MIME-like message, with server information, entity metadata, and possible entity-body content
See the theHTTP/1.1 specification specification for the semantics and nuances of HTTP.children