diff options
author | Anders Svensson <[email protected]> | 2014-11-13 21:56:03 +0100 |
---|---|---|
committer | Anders Svensson <[email protected]> | 2014-11-27 11:19:29 +0100 |
commit | c29dd0129b35390334bb6d2bbed5500b7089a532 (patch) | |
tree | 1f4e6793ccd42e7c087245898a3ebc4c1ba603d1 /lib/stdlib/test/re_SUITE_data | |
parent | 743ed31108ee555db18d9833186865e85e34333e (diff) | |
download | otp-c29dd0129b35390334bb6d2bbed5500b7089a532.tar.gz otp-c29dd0129b35390334bb6d2bbed5500b7089a532.tar.bz2 otp-c29dd0129b35390334bb6d2bbed5500b7089a532.zip |
Order peers in pick_peer callbacks
The order of peers presented to a diameter_app(3) pick_peer callback has
previously not been documented, but there are use cases that are
simplified by an ordering. For example, consider preferring a direct
connection to a specified Destination-Host/Realm to any host in the
realm. The implementation previously treated this as a special case by
placing matching hosts at the head of the peers list, but the
documentation made no guarantees. Now present peers in match-order, so
that the desired sorting is the result of the following filter.
{any, [{all, [host, realm]}, realm]}
The implementation is not backwards compatible in the sense that a realm
filter alone is no longer equivalent in this case. However, as stated,
the documentation never made any guarantees regarding the sorting.
Diffstat (limited to 'lib/stdlib/test/re_SUITE_data')
0 files changed, 0 insertions, 0 deletions