From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeff Garzik <jeff@garzik.org>
Subject: tabled: Some Amazon S3 features to consider
Date: Tue, 06 Jul 2010 16:04:15 -0400
Message-ID: <4C338C3F.3080808@garzik.org>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Return-path: <hail-devel-owner@vger.kernel.org>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:sender:message-id:date:from
         :user-agent:mime-version:to:subject:content-type
         :content-transfer-encoding;
        bh=+Rtc2UJKiEhrJDwyHsZ+DWjXzmmPWao5wzEedl0L6n8=;
        b=xkEn4sJ78X+PDiD1/F607WS5spCylHb1uNWayQBOZ43TjmW9iMV1AbdCtmdjdO0Uoy
         AOYftaSSgEt76e3J1wmV6SrUHyvFe3WC0NE34yJF/L0+OIKJBUTD1SGM6j1vqFa6DVMl
         ZhFc9R12dpXdcP7aMvypbbDJTTPktu78OiAIg=
Sender: hail-devel-owner@vger.kernel.org
List-ID: <hail-devel.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
To: Project Hail <hail-devel@vger.kernel.org>


Here are a few interesting things that have appeared in the S3 API since 
its initial release:

1) Object versioning.  All objects now uniquely identified by (key, 
version) pair.  API compatibility is maintained by supporting the notion 
of "current" version.

2) Object copying.  Rather than an expensive S3->client->S3 round-trip, 
you may supply the x-amz-copy-source header to the PUT operation, 
causing S3 to use an existing object's data as the source for the PUT.

3) Reduced redundancy.  x-amz-storage-class header may used to specify 
normal durability ("STANDARD") or reduced durability ("REDUCED_REDUNDANCY").

4) Regions (localization).  Bucket locations may be set.  Project Hail 
services have some notion of location as well.  See if we can match up 
the two...

5) POST HTTP method.  POST is like PUT, but can be used directly from a 
browser.