All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kyle Bader <kyle.bader@gmail.com>
To: Yehuda Sadeh-Weinraub <yehuda@redhat.com>
Cc: Harshal Gupta <harshal.gupta001@gmail.com>,
	ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Duplicate bucket creation Response in RGW
Date: Thu, 11 Jun 2015 14:22:56 -0700	[thread overview]
Message-ID: <CAFMfnwqsxGyQSE64G6_MsQMdN5PD-yoBsfrujpKxXj2zOQUUsA@mail.gmail.com> (raw)
In-Reply-To: <1688384556.13183297.1434040012831.JavaMail.zimbra@redhat.com>

> I don't see a compelling reason why to change our current behaviour. The fact that Amazon itself is inconsistent makes me think that it just an artifact of their architecture, rather than a carefully designed api.

Interesting.. if we look at the Amazon S3 FAQ we can understand the
differences in API responses:

"Q: What data consistency model does Amazon S3 employ?

Amazon S3 buckets in the US Standard region provide eventual
consistency. Amazon S3 buckets in all other regions provide
read-after-write consistency for PUTS of new objects and eventual
consistency for overwrite PUTS and DELETES."

If we consider buckets in our implementation to be eventually
consistent, we should probably return 200. If we can provide
read-after-write consistency, then we should probably return 209.

-- 

Kyle

  reply	other threads:[~2015-06-11 21:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-10 12:22 Duplicate bucket creation Response in RGW Harshal Gupta
2015-06-10 18:08 ` Yehuda Sadeh-Weinraub
2015-06-11 11:30   ` Harshal Gupta
2015-06-11 16:26     ` Yehuda Sadeh-Weinraub
2015-06-11 21:22       ` Kyle Bader [this message]
2015-06-11 23:51         ` Yehuda Sadeh-Weinraub
2015-06-16 20:24           ` Harshal Gupta
2015-06-18 16:50             ` Harshal Gupta

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=CAFMfnwqsxGyQSE64G6_MsQMdN5PD-yoBsfrujpKxXj2zOQUUsA@mail.gmail.com \
    --to=kyle.bader@gmail.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=harshal.gupta001@gmail.com \
    --cc=yehuda@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.