aboutsummaryrefslogtreecommitdiffstats
path: root/lib/diameter/include
diff options
context:
space:
mode:
authorAnders Svensson <[email protected]>2015-06-21 09:55:17 +0200
committerAnders Svensson <[email protected]>2015-08-05 01:33:33 +0200
commit780ea64fff1bae552510ed419ec2bb011923a5cc (patch)
treed73a1a6621b0473c2655789896bae0d23fd8fe1d /lib/diameter/include
parent82c15a915981842a7013375d2e62d00d775078e1 (diff)
downloadotp-780ea64fff1bae552510ed419ec2bb011923a5cc.tar.gz
otp-780ea64fff1bae552510ed419ec2bb011923a5cc.tar.bz2
otp-780ea64fff1bae552510ed419ec2bb011923a5cc.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.
Diffstat (limited to 'lib/diameter/include')
0 files changed, 0 insertions, 0 deletions