AppSuite:File Storages per User: Difference between revisions
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
= File Storages per user = | = File Storages per user = | ||
This document tries to outline and explain the new concept of having the possibility to specify file storages on a per user basis that is introduced with Open-‐Xchange Server v7.8.0. | |||
== The previous situation == | |||
Before the introduction of the file storages per user feature, it was only possible to specify the file storage association per context. | |||
That file storage was used for all modules/functions that are supposed to store/retrieve files: | |||
* Drive | |||
* Thumbnails | |||
* PIM attachments | |||
* Signature attachments | |||
File storages are registered and maintained in file store table held in configDb database. File storage obtains a unique identifier, a base URI and a size limitation. | |||
For each context a file storage identifier is specified alongside with a context quota that defines how much space that context is allowed to occupy in assigned file storage. Thus the sum of all quotas from those contexts assigned to file storage must not exceed the file storage’s size. | |||
[[Image:file_storage_picture1.png|One file storage per context|800px]] | |||
Revision as of 11:05, 3 August 2015
File Storages per user
This document tries to outline and explain the new concept of having the possibility to specify file storages on a per user basis that is introduced with Open-‐Xchange Server v7.8.0.
The previous situation
Before the introduction of the file storages per user feature, it was only possible to specify the file storage association per context. That file storage was used for all modules/functions that are supposed to store/retrieve files:
- Drive
- Thumbnails
- PIM attachments
- Signature attachments
File storages are registered and maintained in file store table held in configDb database. File storage obtains a unique identifier, a base URI and a size limitation.
For each context a file storage identifier is specified alongside with a context quota that defines how much space that context is allowed to occupy in assigned file storage. Thus the sum of all quotas from those contexts assigned to file storage must not exceed the file storage’s size.
