tahoe-lafs/trac-2024-07-25

our use of the term "bucket" is ambiguous #1522

New issue

Open

opened 2011-09-02 00:32:21 +00:00 by davidsarah · 0 comments

davidsarah commented

2011-09-02 00:32:21 +00:00

Owner

We use "bucket" inconsistently to refer to either the collection of shares on a storage server with a given storage index, or the container for a single share.

When we add the S3 backend, there will also be a collision with S3's use of "bucket", meaning a collection of objects that has its own key namespace and is subject to a given access control and geographical region policy. That will probably will not correspond to a bucket in either of our senses.

We use "bucket" inconsistently to refer to either the collection of shares on a storage server with a given storage index, or the container for a single share. When we add the S3 backend, there will also be a collision with S3's use of "bucket", meaning a collection of objects that has its own key namespace and is subject to a given access control and geographical region policy. That will probably will not correspond to a bucket in either of our senses.

tahoe-lafs added the

labels 2011-09-02 00:32:21 +00:00

tahoe-lafs added this to the undecided milestone 2011-09-02 00:32:21 +00:00

tahoe-lafs added

and removed

labels 2012-03-29 19:38:42 +00:00

Sign in to join this conversation.

No labels

LeastAuthority.com automation

cannot reproduce

code-frontend-cli

code-frontend-ftp-sftp

code-frontend-magic-folder

code-frontend-web

code-peerselection

dev-infrastructure

somebody else's problem

was already fixed

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#1522

No description provided.