Mercurial > prosody-modules
comparison mod_firewall/README.markdown @ 4967:1e8381f0d0a8
mod_firewall: README: Fix grammar and further improve wording
| author | Matthew Wild <mwild1@gmail.com> |
|---|---|
| date | Tue, 28 Jun 2022 16:45:09 +0100 |
| parents | 4ffd6551f4bb |
| children | 84997bc3f92e |
comparison
equal
deleted
inserted
replaced
| 4966:4ffd6551f4bb | 4967:1e8381f0d0a8 |
|---|---|
| 362 | 362 |
| 363 These conditions access the roster of the recipient (only). Therefore they cannot (currently) | 363 These conditions access the roster of the recipient (only). Therefore they cannot (currently) |
| 364 be used in some [chains](#chains), such as for outgoing messages (the recipient may be on another server). | 364 be used in some [chains](#chains), such as for outgoing messages (the recipient may be on another server). |
| 365 | 365 |
| 366 Performance note: these checks can potentially cause storage access (especially if the recipient | 366 Performance note: these checks can potentially cause storage access (especially if the recipient |
| 367 is currently offline), so you may want to limit its use in high-traffic situations, and place rules | 367 is currently offline), so you may want to limit their use in high-traffic situations, and place rules |
| 368 containing a roster check below other rules (such as a rate limiter). The storage access is | 368 containing a roster check below other rules (such as a rate limiter). The storage access is |
| 369 performed unconditionally before the first rule that contains a roster-based condition, even if earlier | 369 performed unconditionally just before evaluation of the first rule that contains a roster-based |
| 370 conditions in that rule do not match. | 370 condition, even if earlier conditions in that rule do not match. |
| 371 | 371 |
| 372 #### IN ROSTER | 372 #### IN ROSTER |
| 373 | 373 |
| 374 Tests whether the sender is in the recipient's roster. | 374 Tests whether the sender is in the recipient's roster. |
| 375 | 375 |