Dell DX6000 설정 및 구성 매뉴얼 - 페이지 40

{카테고리_이름} Dell DX6000에 대한 설정 및 구성 매뉴얼을 온라인으로 검색하거나 PDF를 다운로드하세요. Dell DX6000 43 페이지. Rack installation instructions — static rails
Dell DX6000에 대해서도 마찬가지입니다: 보충 설명서 (4 페이지), 하드웨어 설치 지침 (2 페이지), 사용자 설명서 (46 페이지), 설치 및 구성 매뉴얼 (35 페이지), 시작하기 매뉴얼 (28 페이지), 공지 사항 (28 페이지), 공지 사항 (20 페이지), 개요 (19 페이지), 구성 매뉴얼 (9 페이지), 구성 매뉴얼 (9 페이지), 릴리스 노트 (8 페이지), 참조 매뉴얼 (12 페이지), 구성 매뉴얼 (7 페이지), 릴리스 노트 (6 페이지), 릴리스 노트 (5 페이지), 릴리스 정보 (5 페이지), 설치 지침 (2 페이지), 설치 지침 (2 페이지)

페이지 인쇄

C.3. Enumerator Next

The Enumerator Next command is a request for the next objects in an enumeration which was

previously initiated with an Enumerator Start command. For performance reasons Publisher does

not attempt to retrieve elements in a specific order.

The format of the request is as follows:

GET /<Enumerator UUID>?maxItems=<max-objects-to-retrieve> HTTP/1.1

Host: <publisherhost>

Note the maxItems query argument is only supported for the UUID and Event enumerator types. A

maxItems argument supplied for a Metadata enumerator will be ignored.

C.3.1. Enumerator Next Query Arguments

The following optional query arguments are defined for the Next command only and used to convey

status information about the Enumerator to the Publisher. The Publisher will use some but not all of

this information to update Enumerator status on the Publisher console. See also the Configuration

and Status Query Arguments section below for additional optional arguments that are shared with

the Start method:

Argument Name

upTime

backLog

inProgress

dropped

syncToken

Description

Number of seconds since the subscriber was

started.

Number of items the subscriber is holding that it

has not begun processing.

Number of items the subscriber is actively

processing.

Number of items that the subscriber has failed

to process. The dropped query argument

provides the subscriber a way to report possible

trouble conditions to the Publisher. Subscribers

should take care to only "drop" events after

sufficient retries. Note: Dropped events will

not be resent by the Publisher without manual

intervention using the Republish or Republish

All commands from the Publisher Console.

The value of the Content-Sync-Token header

from the last successfully received Start or Next

response. The Content-Sync-Token is used to

confirm with the Publisher that a request was

successfully received and ensure UUIDs are

not missed due to a network or connectivity

issue. If the syncToken matches the one

expected by the Publisher from the previous

request, the next set of requested UUIDs will

be sent. If the syncToken does not match, the

Publisher will resend the previous set of UUIDs.

If the syncToken is not present on the request,

the Publisher will automatically send the next

set of requested UUIDs.

Version 2.2

December 2010