[sr-dev] git:master:79d07fe0: modules: readme files regenerated - presence ... [skip ci]

[Kamailio Dev]

Module: kamailio
Branch: master
Commit: 79d07fe00af8e30910a4e1b23b641ebcc96f0895
URL: https://github.com/kamailio/kamailio/commit/79d07fe00af8e30910a4e1b23b641ebcc96f0895

Author: Kamailio Dev <kamailio.dev at kamailio.org>
Committer: Kamailio Dev <kamailio.dev at kamailio.org>
Date: 2020-04-20T17:31:14+02:00

modules: readme files regenerated - presence ... [skip ci]

---

Modified: src/modules/presence/README

---

Diff:  https://github.com/kamailio/kamailio/commit/79d07fe00af8e30910a4e1b23b641ebcc96f0895.diff
Patch: https://github.com/kamailio/kamailio/commit/79d07fe00af8e30910a4e1b23b641ebcc96f0895.patch

---

diff --git a/src/modules/presence/README b/src/modules/presence/README
index d0f3e6fa1a..c4ba8ca1b1 100644
--- a/src/modules/presence/README
+++ b/src/modules/presence/README
@@ -604,12 +604,18 @@ modparam("presence", "subs_db_mode", 1)
 
 3.19. publ_cache (int)
 
-   To improve performance, the presence module holds by default a publish
-   cache that says if a certain publication exists in database. This is
-   only a list of URI + event, so it does not use much memory. The cache
-   is used when a Subscription is received to check if there is any
-   published state in database. This way unnecessary queries in presentity
-   table are avoided.
+   To improve performance, the presence module can operate in a couple of
+   modes related to how PUBLISH data is stored. If publ_cache is 0, then
+   no information is store in memory.
+
+   If publ_cache is 1, then the module keeps in memory an index of the
+   records stored in database, In this mode it keeps only the list of URIs
+   and events, so it does not use much memory. The cache is used when a
+   Subscription is received to check if there is any published state in
+   database. This way unnecessary queries in presentity table are avoided.
+
+   If publ_cache is 2, then the module keeps everything related to PUBLISH
+   requests in memory, not storing anything in the database.
 
    Setting this parameter to 0 will disable the usage of the publish
    cache. This is desirable when you have more servers sharing the same