aboutsummaryrefslogtreecommitdiffstats
path: root/lib/diameter/test/diameter_util.erl
diff options
context:
space:
mode:
authorAnders Svensson <[email protected]>2015-06-21 09:55:17 +0200
committerAnders Svensson <[email protected]>2015-06-21 11:03:07 +0200
commitfc9e8a6bade31c7216a8d6a194ba221f6f15459c (patch)
tree6e8c4638235458e05e531bc6a9d3e142ccd2d8b9 /lib/diameter/test/diameter_util.erl
parent1f483bd5eb6371a1bf2517188658cc4a9cb57cae (diff)
downloadotp-fc9e8a6bade31c7216a8d6a194ba221f6f15459c.tar.gz
otp-fc9e8a6bade31c7216a8d6a194ba221f6f15459c.tar.bz2
otp-fc9e8a6bade31c7216a8d6a194ba221f6f15459c.zip
Fix start order of alternate transports
A transport configured with diameter:add_transport/2 can be passed multiple transport_module/transport_config tuples in order to specify alternate configuration, modules being attempted in order until one succeeds. This is primarily for the connecting case, to allow a transport to be configured to first attempt connection over SCTP, and then TCP in case SCTP fails, with configuration like that documented: {transport_module, diameter_sctp}, {transport_config, [...], 5000}, {transport_module, diameter_tcp}, {transport_config, [...]} If the options are the same in both cases, another possibility would be configuration like this, which attaches the same transport_config to both modules: {transport_module, diameter_sctp}, {transport_module, diameter_tcp}, {transport_config, [...], 5000}, However, in this case the start order was reversed relative to the documented order: first tcp, then sctp. This commit restores the intended order. OTP-12851
Diffstat (limited to 'lib/diameter/test/diameter_util.erl')
0 files changed, 0 insertions, 0 deletions