| /* |
| * Licensed to the Apache Software Foundation (ASF) under one or more |
| * contributor license agreements. See the NOTICE file distributed with |
| * this work for additional information regarding copyright ownership. |
| * The ASF licenses this file to You under the Apache License, Version 2.0 |
| * (the "License"); you may not use this file except in compliance with |
| * the License. You may obtain a copy of the License at |
| * |
| * http://www.apache.org/licenses/LICENSE-2.0 |
| * |
| * Unless required by applicable law or agreed to in writing, software |
| * distributed under the License is distributed on an "AS IS" BASIS, |
| * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. |
| * See the License for the specific language governing permissions and |
| * limitations under the License. |
| */ |
| package org.jclouds.s3.domain; |
| |
| import com.google.common.base.CaseFormat; |
| |
| /** |
| * Specifies who pays for the download and request fees. |
| * <p/> |
| * In general, bucket owners pay for all Amazon S3 storage and data transfer costs associated with |
| * their bucket. A bucket owner, however, can configure a bucket to be a Requester Pays bucket. With |
| * Requester Pays buckets, the requester instead of the bucket owner pays the cost of the request |
| * and the data download from the bucket. The bucket owner always pays the cost of storing data. |
| * <p/> |
| * Typically, you configure buckets to be Requester Pays when you want to share data but not incur |
| * charges associated with others accessing the data. You might, for example, use Requester Pays |
| * buckets when making available large data sets, such as zip code directories, reference data, |
| * geospatial information, or web crawling data. |
| * <h3>Important</h3> If you enable Requester Pays on a bucket, anonymous access to that bucket is |
| * not allowed. |
| * <p/> |
| * You must authenticate all requests involving Requester Pays buckets. The request authentication |
| * enables Amazon S3 to identify and charge the requester for their use of the Requester Pays |
| * bucket. |
| * <p/> |
| * After you configure a bucket to be a Requester Pays bucket, requesters must include |
| * x-amz-request-payer in their requests either in the header, for POST and GET requests, or as a |
| * parameter in a REST request to show that they understand that they will be charged for the |
| * request and the data download. |
| * <p/> |
| * Requester Pays buckets do not support the following. |
| * <ul> |
| * <li>Anonymous requests</li> |
| * <li>BitTorrent</li> |
| * <li>SOAP requests</li> |
| * </ul> |
| * |
| * You cannot use a Requester Pays bucket as the target bucket for end user logging, or vice versa. |
| * However, you can turn on end user logging on a Requester Pays bucket where the target bucket is a |
| * non Requester Pays bucket. |
| */ |
| public enum Payer { |
| REQUESTER, BUCKET_OWNER, UNRECOGNIZED; |
| |
| public String value() { |
| return CaseFormat.UPPER_UNDERSCORE.to(CaseFormat.UPPER_CAMEL, name()); |
| } |
| |
| public static Payer fromValue(String payer) { |
| try { |
| return valueOf(CaseFormat.UPPER_CAMEL.to(CaseFormat.UPPER_UNDERSCORE, payer)); |
| } catch (IllegalArgumentException e) { |
| return UNRECOGNIZED; |
| } |
| } |
| } |