Dell DX6012S Manuel d'installation et de configuration - Page 41

Parcourez en ligne ou téléchargez le pdf Manuel d'installation et de configuration pour {nom_de_la_catégorie} Dell DX6012S. Dell DX6012S 43 pages. Rack installation instructions — static rails
Également pour Dell DX6012S : Manuel complémentaire (4 pages), Instructions pour l'installation du matériel (2 pages), Manuel de l'utilisateur (46 pages), Manuel d'installation et de configuration (35 pages), Manuel de démarrage (28 pages), Avis (28 pages), Avis (20 pages), Vue d'ensemble (19 pages), Manuel de configuration (9 pages), Manuel de configuration (9 pages), Note de mise à jour (8 pages), Manuel de configuration (7 pages), Note de mise à jour (6 pages), Note de mise à jour (5 pages), Notes de mise à jour (5 pages), Manuel de démarrage (47 pages), Installation (2 pages), Installation du rack (2 pages)

C.3.2. Enumerator Next Response

A typical normal response to an Enumerator Next command of type UUID or Event is:

HTTP/1.1 200

Date: ...

Server: Content Router Publisher

Content-Type: text/plain

Content-Length: <bytes in response body>

Content-Sync-Token: <token value>

For a Metadata Enumerator, the response has an additional "Content-UUID" header containing the

object's UUID.

HTTP/1.1 200

Date: ...

Server: Content Router Publisher

Content-UUID: <UUID of object>

Content-Type: text/plain

Content-Length: <bytes in response body>

Content-Sync-Token: <token value>

The content and format of each line of the response body varies by enumerator type as follows:

• UUID enumerators: "<object uuid>"

• Event enumerators: "UUID,<evType>" , where evType equals event types of 1 (deleted), 2

(created), or 4 (created/updated for anchor streams) (3 is not currently utilized)

• Metadata enumerators: "<header name>: <value>" (for each header present on the object)

Metadata enumerators will only contain metadata for a single object, but UUID and Event

enumerators support inclusion of data for multiple objects. If for any reason the request is not

successful, a 404 response code will be returned with a descriptive message in the response body

as to the encountered problem.

C.4. Enumerator End

The Enumerator End command is called to end an enumeration which was previously initiated with

an Enumerator Start command. The format of the request is as follows:

DELETE /<Enumerator UUID> HTTP/1.1

Host: <publisherhost>

C.4.1. End Response

The normal response to an Enumerator End command is:

HTTP/1.1 200

Date: ...

Server: Content Router Publisher

Content-Type: text/plain

Content-Length: ...

Object Enumerator deleted

Version 2.2

December 2010