Dell DX6004S DX Object Storage SCSP Proxy Overview - Page 8

Note Because you are working with the default cluster domain, the domain name does not need to be sent as the Host in the request. For unnamed objects, POST authentication is supported only in the default cluster domain. • Remote synchronous write POST of an unnamed object to the default cluster domain, which has POST authentication enabled POST /_proxy/cluster-name/?replicate=immediate For more information about remote synchronous write, see the next section. 1.2.2. Remote Synchronous Writes and Updates Remote Synchronous Write enables you to write or update a copy of the same stream both locally and remotely as part of the same request. A Remote Synchronous Write first writes two copies of the object to the local cluster. If the local write fails for any reason, the error response is returned to the requestor and the operation is abandoned. If the local write succeeds, the Proxy writes the updated object to the specified remote cluster. This request is authenticated using the DX Storage administrator credentials specified in the configuration of the remote cluster. All query arguments except alias=yes as well as the Expect: Content-MD5 header are stripped from the remote write to simplify the response coordination between the two clusters. If the remote write is also successful, a 201 (Created) response is returned to the requestor. If the remote write fails for any reason, a 202 (Accept) response is returned, indicating that only the local write was successful and that remote replication can occur at a later time using DX Content Router (if enabled). 1.2.3. Remote Aggregate Info The Proxy has an AggregateInfo method to validate that a set of content exists in a cluster. Aggregate Info can be issued against a local cluster but it is usually used to validate remote replication. You determine the desired data set by first creating a "consistency checkpoint" using the following format, terminated with CRLF: {uuid [mutable | immutable] | url-encoded-name} For unnamed anchor streams, you must use mutable parameter. (The default, with no parameter specified, is immutable.) All named objects are assumed to be mutable so no argument is required. You must supply a list of either URL-encoded names or UUIDs. (Use percent encoding for object names, if needed.) The name, UUID, or the consistency checkpoint, is stored as a DX Storage object. Info requests in the AggregateInfo method are issued for each name or UUID in the consistency checkpoint and either object metadata or an error response is returned in the concatenated Copyright © 2010 Caringo, Inc. All rights reserved 5 Version 1.2 December 2010