You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In alignment with the goal of enabling data organization by web developers ("Allow web applications to evict slices of data"), should buckets be nestable?
Hypothetical use case: an email client that allows multiuser sign-in, and organizes each user's data into multiple buckets, such as drafts and inbox. The drafts bucket would be a child bucket of the user-1234 bucket.
Behavior: deleting a parent bucket should delete child buckets. Unspecified bucket policies should default to parent bucket policy values.
The text was updated successfully, but these errors were encountered:
I think the answer here would depend on reaching a conclusion for the discussion in #36 about the minimum and maximum number of buckets we expect browsers to support. If we can only guarantee origins 10 buckets, there's little point in adding a concept of hierarchy and having to deal with the dependency graph that would result.
In alignment with the goal of enabling data organization by web developers ("Allow web applications to evict slices of data"), should buckets be nestable?
Hypothetical use case: an email client that allows multiuser sign-in, and organizes each user's data into multiple buckets, such as
drafts
andinbox
. Thedrafts
bucket would be a child bucket of theuser-1234
bucket.Behavior: deleting a parent bucket should delete child buckets. Unspecified bucket policies should default to parent bucket policy values.
The text was updated successfully, but these errors were encountered: