tileStorages


URI

<managerRoot uri>/storages[.<format>]

Supported methods

GET, POST, HEAD

Parent resource

managerRoot

Child resources

tileStorage

Introduction

The tile storage resource list. You can create a new tileStorage resource through the POST request.

Supported Methods:

Supported output formats: rjson, json, html, xml.

Resource hierarchy

HTTP request methods

Implement the HTTP request on the following URI, where supermapiserver is the server name, with rjson being the output format.

http://supermapiserver:8090/iserver/manager/storages.rjson

GET request

Gets all current tile storage configuration information list.

Response structure

A tile storage configuration information list will be returned by implementing the GET request on the tileStorages resource. The representation structure of storage configuration information of a single tile will be as follows:  

Field Type Description
id String The tile storage ID.
tileSourceInfo tileSourceInfo The tile storage configuration information.

Response example

The returned rjson format representation after implementing the GET request on the tileStorages resource http://localhost:8090/iserver/manager/storages.rjson is as follows:

[

    {

        "id": "aa",

        "tileSourceInfo": {

            "fdfsTrackers": ["192.168.122.44:22122"],

            "fdhtGroups": [["192.168.122.44:11411"]],

            "type": "FastDFS"

        }

    },

    {

        "id": "bb",

        "tileSourceInfo": {

            "fdfsTrackers": ["192.168.122.44:22122"],

            "fdhtGroups": [["192.168.122.44:11411"]],

            "type": "FastDFS"

        }

    }

]

POST request

Creates a new tileStorage resource.

Request parameter

To implement the POST request on the tileStorages resource to add one new tileStorage resource, following parameters need to be included in the request body:

Name Type Description
id String The tile storage ID.
tileSourceInfo tileSourceInfo The tile storage configuration information.

Response structure

The returned representation structure is as follows after implementing the POST request on the tileStorages resource (representation is in the entity body of the response message):   

Field Type Description
newResourceID String The ID of the newly added storage resource.
newResourceLocation String The address of the new storage resource on the sever after adding the tileStorage successfully.
postResultType enum The result type of the POST request. "CreateChild" indicates creating new child resource.
succeed boolean Whether the tileStorage resource has been added successfully, with true indicating the operation of adding tileStorage successfully.

Example usage

Suppose we implement the POST request with the following request body on the tileStorages resource http://localhost:8090/iserver/manager/storages.rjson to add a new tileStorage resource.

{

    "id": "aa",

    "tileSourceInfo": {

        "fdfsTrackers": ["192.168.122.44:22122"],

        "fdhtGroups": [

            ["192.168.122.44:11411"]

        ],

        "type": "FastDFS"

    }

}

The response result returned in rjson format is as follows:

{

    "newResourceID": "aa",

    "newResourceLocation": "http://localhost:8090/iserver/manager/storages/aa.rjson",

    "postResultType": "CreateChild",

    "succeed": true

}

HEAD request

Asks for the response identical to the one that would correspond to a GET request, but without the response body. This is useful for retrieving meta-information written in response headers, without having to transport the entire content. The meta-information includes the media-type, content-encoding, transfer-encoding, content-length, etc.

HEAD request can be used to check if the tileStorages resource exists, or if the tileStorages resource can be accessed by clients. It can also determine if the tileStorages resource supports an output format <format> if performed on a URI with .<format> included.

See