[Imported from Trac: page QuotaManagement, version 3]
parent
88da2b5039
commit
fb39c42194
|
@ -1,12 +1,13 @@
|
|||
|
||||
|
||||
Quota management is about protecting the Storage Servers. Given a limited
|
||||
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
|
||||
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.
|
||||
|
||||
There are roughly three different approaches to this: secret-based,
|
||||
private-key-based, and FURL-based. From certain points of view, these are all
|
||||
There are roughly three different approaches to this: **secret-based**,
|
||||
**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
|
||||
create attenuated capabilities on demand, which is kind of like an asymmetric
|
||||
form of hash derivation. The differences consist of tradeoffs between CPU
|
||||
|
|
Loading…
Reference in a new issue