tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

[Imported from Trac: page QuotaManagement, version 3]

imhavoc 2009-12-09 19:31:33 +00:00
parent 88da2b5039
commit fb39c42194
1 changed files with 3 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
QuotaManagement.md

@ -1,12 +1,13 @@
Quota management is about protecting the Storage Servers. Given a limited Quota management is about protecting the Storage Servers. Given a limited
amount of storage space, how should it be allocated between the users? The amount of storage space, how should it be allocated between the users? The
admin of a server may give out space in exchange for money, for other storage admin of a server may give out space in exchange for money, for other storage
space, or out of friendship, but many use cases work better if the admin can space, or out of friendship, but many use cases work better if the admin can
track and control how much space any given user can consume. track and control how much space any given user can consume.
There are roughly three different approaches to this: secret-based, There are roughly three different approaches to this: **secret-based**,
private-key-based, and FURL-based. From certain points of view, these are all **private-key-based**, and **FURL-based**. From certain points of view, these are all
equivalent: a private key is like a remote capability that can be used to equivalent: a private key is like a remote capability that can be used to
create attenuated capabilities on demand, which is kind of like an asymmetric create attenuated capabilities on demand, which is kind of like an asymmetric
form of hash derivation. The differences consist of tradeoffs between CPU form of hash derivation. The differences consist of tradeoffs between CPU