MAILBOX-291 Fix use of punctuation on the quota's website page
Project: http://git-wip-us.apache.org/repos/asf/james-project/repo Commit: http://git-wip-us.apache.org/repos/asf/james-project/commit/6a8b56bf Tree: http://git-wip-us.apache.org/repos/asf/james-project/tree/6a8b56bf Diff: http://git-wip-us.apache.org/repos/asf/james-project/diff/6a8b56bf Branch: refs/heads/master Commit: 6a8b56bf0b6f6e53511785a42e76e7652cfda20d Parents: 54c6402 Author: benwa <btell...@linagora.com> Authored: Thu Mar 30 08:09:41 2017 +0700 Committer: benwa <btell...@linagora.com> Committed: Fri Mar 31 08:46:26 2017 +0700 ---------------------------------------------------------------------- server/src/site/xdoc/config-quota.xml | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/james-project/blob/6a8b56bf/server/src/site/xdoc/config-quota.xml ---------------------------------------------------------------------- diff --git a/server/src/site/xdoc/config-quota.xml b/server/src/site/xdoc/config-quota.xml index f8e88da..74e6d34 100644 --- a/server/src/site/xdoc/config-quota.xml +++ b/server/src/site/xdoc/config-quota.xml @@ -43,23 +43,23 @@ </p> <p> - James' implementation is split in different components, and each one of them gets its own responsibility : + James' implementation is split in different components, and each one of them gets its own responsibility: <ul> - <li>Quota Root Resolver : This component is responsible of the correspondence between mailboxes and QUOTA ROOT. A default implementation is + <li>Quota Root Resolver: This component is responsible of the correspondence between mailboxes and QUOTA ROOT. A default implementation is available and simply group mailboxes in QUOTA ROOT on the base of the owner name.</li> - <li>Quota Manager : This component retrieves quota associated with a QUOTA ROOT. A store implementation is available and relies on other components. + <li>Quota Manager: This component retrieves quota associated with a QUOTA ROOT. A store implementation is available and relies on other components. A fake implementation is available in order to add no overhead.</li> - <li>Max Quota Manager : This component retrieves maximum values associated with quotas and gives a way to potentially + <li>Max Quota Manager: This component retrieves maximum values associated with quotas and gives a way to potentially (depending on the implementation) update these per QUOTA ROOT maximum values. Four implementations are available for now. A NoQuotaManager implementation is read only and returns UNLIMITED maximum values. FixedMaxQuotaManager returns one and only one value for all user. You can configure these maximum values threw the configuration files. A InMemoryPerUserMaxQuotaManager allows you to configure quota for each QUOTA ROOT. Note that it needs to be done threw configuration to be persistent. We provide some other implementation: A Cassandra implementation allows to store maximum quota values in Cassandra, and a JPA implementation.</li> - <li>Current Quota Manager : This component can be omitted if you are running a fake QUOTA manager. inmemory implementation is an event updated cache on + <li>Current Quota Manager: This component can be omitted if you are running a fake QUOTA manager. inmemory implementation is an event updated cache on top of a Quota calculator (that fetches every e-mail metadata of every mailboxes belonging to the QUOTA ROOT: it is expensive). Cassandra and Jpa implementations are also available.</li> - <li>Quota Updater : This components allows to update current quota values. A fake implementation is available. A real, event base solution also exists.</li> + <li>Quota Updater: This components allows to update current quota values. A fake implementation is available. A real, event base solution also exists.</li> </ul> </p> @@ -68,7 +68,7 @@ </p> <p> - Quota integration consists of : + Quota integration consists of: <ul> <li>Checks in the message manager. An operation that will bring the QUOTA ROOT over quota will be dropped. APPEND and COPY operations are concerned.</li> @@ -80,13 +80,13 @@ </p> <p> - The administration of QUOTAs can be done : + The administration of QUOTAs can be done: <ul> <li>Threw configuration file. Note that this is required to persist a change made to the inmemory or fixed Max Quota Manager. It needs a James reboot to take effect. Finally, using configuration file for setting maximum quota values will override CLI set values. Avoid this option this persistent Max Quota Manager (for instance Cassandra)</li> - <li>Threw the CLI : offers immediate configuration changes on quota maximum values. Note that if you are using either a + <li>Threw the CLI: offers immediate configuration changes on quota maximum values. Note that if you are using either a fixed or inmemory Max QUota Manager, your changes need to be done to the XML configuration to be persisted.</li> </ul> </p> --------------------------------------------------------------------- To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
