hail-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Project Hail <hail-devel@vger.kernel.org>
Subject: tabled's status, and S3 API compliance
Date: Fri, 05 Mar 2010 19:51:50 -0500	[thread overview]
Message-ID: <4B91A726.607@garzik.org> (raw)


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



                 reply	other threads:[~2010-03-06  0:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B91A726.607@garzik.org \
    --to=jeff@garzik.org \
    --cc=hail-devel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).