Dell DX6004S Manuel d'installation et de configuration - Page 39

Parcourez en ligne ou téléchargez le pdf Manuel d'installation et de configuration pour {nom_de_la_catégorie} Dell DX6004S. Dell DX6004S 43 pages. Document
Également pour Dell DX6004S : Manuel complémentaire (4 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 (49 pages)

Imprimer la page
Dell DX6004S Manuel d'installation et de configuration
POST /<channel>?type=<enumerator type>&start=<date-time1>&end=<date-time2>
HTTP/1.1
Host: <publisherhost>
Here channel is the "subscription name" as specified when configuring a DX Content Router
replicator service. It corresponds to one of the sets of filter rules identified by a select tag in the
publisher rules.xml file. The start and end parameters delimit the create dates of objects to be
enumerated for metadata and UUID enumerator types. Event type enumerators do not support
start and end dates. Both dates are ISO 8601 date-time values; RFC 1123 formatted date-time
values are not yet supported. The time-of-day specification may be omitted, in which case the time
00:00:00 is assumed. The start date-time is inclusive, the end date-time non-inclusive.
C.2.1. Enumerator Start Query Arguments
The following query arguments are supported for the Start command. The Publisher saves all
provided query arguments so arguments need not be supplied with every call after the initial one
unless a change is desired.
Argument Name
type
start
end
C.2.2. Enumerator Start Response
The normal response to an Enumerator Start command is:
HTTP/1.1 201
Date: ...
Server: Content Router Publisher
Content-UUID: 41a140b5271dc8d22ff8d027176a0821
Content-Sync-Token: <token value>
Content-Type: text/plain
Content-Length: <bytes in response body>
Object Enumerator created - channel: '<channel name>', type:
'<enumerator type>'[,start: '<date-time1>'][, end: '<date-time2>']
The Content-UUID header contains a generated UUID identifying the enumerator instance created.
The Content-Sync-Token is used by the Next command to indicate the previous request was
successfully received. The (optional) start/end date-times in the response body are displayed as
unix epoch time seconds. 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.
Copyright © 2010 Caringo, Inc.
All rights reserved
Description
The case-insensitive value for enumerator type:
Metadata, UUID or Event.
An ISO 8601 formatted date-time string that
corresponds to the start of the time range
that should be enumerated. All time stamp
comparisons are based on file creation
timestamps.
An ISO 8601 formatted date-time string that
corresponds to the end of the time range
that should be enumerated. All time stamp
comparisons are based on file creation
timestamps.
35
Version 2.2
December 2010