Dell DX6004S DX Content Router Setup and Configuration Guide - Page 41

C.4. Enumerator End

Get Dell DX6004S PDF manuals and user guides View all Dell DX6004S manuals
Add to My Manuals
Save this manual to your list of manuals

Page 41 highlights

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: Content-Sync-Token: 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: Content-Type: text/plain Content-Length: Content-Sync-Token: The content and format of each line of the response body varies by enumerator type as follows: • UUID enumerators: "" • Event enumerators: "UUID," , where evType equals event types of 1 (deleted), 2 (created), or 4 (created/updated for anchor streams) (3 is not currently utilized) • Metadata enumerators: ": " (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 / HTTP/1.1 Host: 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

  • 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
Copyright © 2010 Caringo, Inc.
All rights reserved
37
Version 2.2
December 2010
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