From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeff Garzik <jeff@garzik.org>
Subject: tabled's status, and S3 API compliance
Date: Fri, 05 Mar 2010 19:51:50 -0500
Message-ID: <4B91A726.607@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=v2lNWZplfhO117kUq+49ALJ44kiIGYRUbPs9GM3KquU=;
        b=CF3StTux5n1zuuiIm2daI7catXlQTIQdMuFyh0Yzy0njPmHLDAFoQ3P07FYunSMfhL
         2BSjAPPvOB9+gR7bVkE+etx0mWDdxIjJxOyPPp06Z1JZdGEWL3lPNIRc7E3Wg5qCSPdO
         MGfK7CMX61YtsDmiT27rJUni+qQdeR1rbiNCM=
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>


I made a pass through the S3 API docs (version 2006-03-01), and noted 
everything that tabled is missing.  It is a surprisingly small list:
http://hail.wiki.kernel.org/index.php/Tabled#S3_API_compliance

tabled's status was also updated to "Beta" to reflect its maturity:
http://hail.wiki.kernel.org/index.php/Tabled#Status

The remaining S3 API compliance items I would consider necessary for a 
v1.0 release are

* Partial object retrieval, and the Range HTTP header
	-> not difficult, but not trivial either
* Server access logging
	-> pretty easy, just need to gather all the needed data
* Complete ACL support
	-> our ACL support is usable already, so not a big task

All in all, tabled is looking pretty darned good.  A real release by 
this summer is not out of the question.

	Jeff