Dell DX6004S 개요 - 페이지 7

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

Dell DX6004S 개요
Syntax
/_proxy/remote/uuid-or-name
Note
Support for remote proxy requests without the _proxy/ prefix is deprecated in this
release and will be removed altogether in a future release.

1.2.1. Examples of using /_proxy Syntax

As the following examples show, you must separate the URI from the domain specification using the
slash character (/). In all cases, except where noted, the domain name must be passed as the Host
in the request.
Examples follow:
• AggregateInfo of domain on either a local or remote cluster
Local cluster: GET /_proxy/uuid?indirect=HEAD
Remote cluster: GET /_proxy/cluster-name/uuid?indirect=HEAD
For more information about AggregateInfo, see
• HEAD of a domain on either a remote or any cluster
Remote cluster: HEAD /_proxy/remote?domain=domain-name
Any cluster: HEAD /_proxy/any?domain=domain-name
Note
The domain= query argument is required whenever you perform an operation (in this
case, HEAD) on a domain.
• POST of an unnamed object to the default cluster domain
POST /_proxy/cluster-name/
Copyright © 2010 Caringo, Inc.
All rights reserved
Description
If the object exists in the local cluster the information
is returned. Otherwise, the request is sent to each
remote cluster in random order. If no cluster is able
to locate the data, the error response from the local
server is returned.
remote is valid only for remote INFO requests and
results in an error if used with any other method.
remote causes a request for an object to be sent,
referenced by UUID or by name, to a remote cluster.
The information is returned from the first cluster
that has the object. If the object cannot be found in
any of the remote clusters, the error response that
was received from the first remote cluster tried is
returned.
Section 1.2.3, "Remote Aggregate
4
Info".
Version 1.2
December 2010