Dell DX6004S Panduan Penyiapan dan Konfigurasi - Halaman 41

Jelajahi secara online atau unduh pdf Panduan Penyiapan dan Konfigurasi untuk Server Dell DX6004S. Dell DX6004S 43 halaman. Document
Juga untuk Dell DX6004S: Panduan Tambahan (4 halaman), Panduan Pengguna (46 halaman), Panduan Instalasi dan Konfigurasi (35 halaman), Panduan Memulai (28 halaman), Pemberitahuan (28 halaman), Pemberitahuan (20 halaman), Ikhtisar (19 halaman), Panduan Konfigurasi (9 halaman), Panduan Konfigurasi (9 halaman), Catatan Rilis (8 halaman), Panduan Konfigurasi (7 halaman), Catatan Rilis (6 halaman), Catatan Rilis (5 halaman), Catatan Rilis (5 halaman), Panduan Memulai (49 halaman)

Halaman Cetak
Dell DX6004S Panduan Penyiapan dan Konfigurasi
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
Copyright © 2010 Caringo, Inc.
All rights reserved
37
Version 2.2
December 2010