diff options
author | Anders Svensson <[email protected]> | 2016-01-27 14:20:24 +0100 |
---|---|---|
committer | Anders Svensson <[email protected]> | 2016-01-27 14:20:24 +0100 |
commit | 6301ceeb265f68b417bb2ce58312e34b9557a294 (patch) | |
tree | 8bd0de39225a28160d277197af5c3e46c8340938 /lib/diameter/doc/src/diameter.xml | |
parent | 7e0c7a29f74e855359eb49cb2c231f592e237197 (diff) | |
parent | b8c6a1196f0be5a2e98429797b43c24784bcafca (diff) | |
download | otp-6301ceeb265f68b417bb2ce58312e34b9557a294.tar.gz otp-6301ceeb265f68b417bb2ce58312e34b9557a294.tar.bz2 otp-6301ceeb265f68b417bb2ce58312e34b9557a294.zip |
Merge branch 'maint'
Diffstat (limited to 'lib/diameter/doc/src/diameter.xml')
-rw-r--r-- | lib/diameter/doc/src/diameter.xml | 22 |
1 files changed, 13 insertions, 9 deletions
diff --git a/lib/diameter/doc/src/diameter.xml b/lib/diameter/doc/src/diameter.xml index 61b7fd1337..5cb29c80e3 100644 --- a/lib/diameter/doc/src/diameter.xml +++ b/lib/diameter/doc/src/diameter.xml @@ -467,7 +467,7 @@ Matches only those peers whose Origin-Host has the specified value, or all peers if the atom <c>any</c>.</p> </item> -<tag><c>{realm, any|&dict_DiameterIdentity;</c></tag> +<tag><c>{realm, any|&dict_DiameterIdentity;}</c></tag> <item> <p> Matches only those peers whose Origin-Realm has the @@ -500,18 +500,22 @@ Matches only those peers matched by each filter in the specified list.</p> <item> <p> Matches only those peers matched by at least one filter in the -specified list.</p> +specified list. +The resulting list will be in match order, peers matching the +first filter of the list sorting before those matched by the second, +and so on.</p> +</item> +<tag><c>{first, [&peer_filter;]}</c></tag> +<item> <p> -The resulting peer list will be in match order, peers matching the -first filter of the list sorting before those matched by the second, -and so on. -For example, the following filter causes peers matching both the host -and realm filters to be presented before those matching only the realm -filter.</p> +Like <c>any</c>, but stops at the first filter for which there are +matches, which can be much more efficient when there are many peers. +For example, the following filter causes only peers best matching +both the host and realm filters to be presented.</p> <pre> -{any, [{all, [host, realm]}, realm]} +{first, [{all, [host, realm]}, realm]} </pre> </item> |